What's New in Orbittest Client 1.0.1

Orbittest Client v1.0.1 (2026-06-17) brings four new capabilities to the local-first API testing workstation: OAuth 2.0 authentication, a real code editor for scripts and bodies, live variable autocomplete, and a command-line runner for CI pipelines.

Auto-update

Existing installs update themselves in the background — you don’t need to do anything. Prefer a manual install? Grab the signed Windows installer from the v1.0.1 release page.

At a glance

OAuth 2.0 authentication

Request, store, and attach access tokens from the auth editor — no more hand-pasted bearer tokens.

Syntax-highlighted editor

JavaScript highlighting for pre-request scripts, test scripts, and request bodies.

Variable autocomplete

Live {{variable}} scanning with inline autocomplete across the request builder.

Command-line runner

Run collections from the terminal with JSON / JUnit output — built for CI.

---

OAuth 2.0 authentication New

Until now, calling a protected API meant generating a token somewhere else and pasting it into a header by hand — then doing it again every time the token expired. In v1.0.1, Orbittest Client can request, store, and attach OAuth 2.0 access tokens for you, directly from the request’s Auth tab.

How it works

1. Open a request and select the Auth tab.

2. Choose OAuth 2.0 as the authorization type.

3. Fill in the token details for your provider — typically the token endpoint URL, client ID, client secret, scope, and the grant type (for example Authorization Code or Client Credentials). Any field accepts {{variables}}, so you can keep secrets in an environment instead of the request.

4. Click Request Token. Orbittest Client performs the token exchange and stores the resulting access token with the request.

5. Send the request. The stored token is attached automatically as an Authorization: Bearer … header — you never copy or paste it.

Note

Tokens are kept locally with the rest of your workspace. When a token is no longer valid, just press Request Token again to fetch a fresh one. Because every field supports {{variables}}, the same OAuth configuration works across dev, staging, and prod simply by switching the active environment.

Pair it with the PKCE flow

If your provider uses the Authorization Code flow, see our explainer on the Authorization Code flow with PKCE to understand what the token exchange is doing under the hood.

---

Syntax-highlighted code editor New

Scripts and bodies now open in a real code editor with JavaScript syntax highlighting instead of a plain text box. Highlighting applies in three places:

• Pre-request scripts — run before the request is sent.
• Test scripts — run after the response arrives, to assert on it.
• Request bodies — for raw JSON and JavaScript payloads.

This makes it far easier to spot a missing bracket, an unterminated string, or a typo before you run anything.

Example: a pre-request script

Pre-request script

// Compute a timestamp and stash it for the request to use.
const now = Date.now();
ot.variables.set('requestedAt', String(now));

Example: a test script

Test script

// Assert on the response after it arrives.
ot.test('status is 200', () => {
  ot.expect(ot.response.status).toBe(200);
});

ot.test('body has an id', () => {
  const body = ot.response.json();
  ot.expect(body.id).toBeDefined();
});

Note

Scripts still execute in the same network-isolated sandbox worker as before — no DOM, no bridge, and a hard timeout. The editor only changes how you write them, not how they run.

---

Variable autocomplete New

Orbittest Client now scans your variables live — from the active environment, the collection, and any data-driven row — and offers inline autocomplete as you type. Start typing {{ in almost any field and a dropdown of matching variable names appears; pick one and it’s inserted complete.

Autocomplete is available across the request builder, including:

• the URL and query params
• headers and the OAuth fields
• the request body
• pre-request and test scripts

Variables resolve everywhere

GET {{baseUrl}}/users/{{userId}}
Authorization: Bearer {{accessToken}}

This removes the two most common variable bugs: misremembering a name, and referencing a variable that doesn’t exist in the current scope.

---

Command-line runner New

A new CLI runs your saved collections and requests straight from the terminal — no UI required. It’s scriptable, returns proper exit codes, and emits JSON and JUnit reports, which makes it a natural fit for CI pipelines.

Run a collection

Run a collection

orbittest-client run "My Collection" --env staging

Common options

Option	What it does
--env <name>	Run with a named environment’s variables.
--data <file>	Drive the run from a CSV / JSON data file (one iteration per row).
--reporter <list>	Output format(s): json, junit, or both (comma-separated).
--out <dir>	Directory to write report files into.
--bail	Stop on the first failing request.

JSON and JUnit reports

Emit CI-friendly reports

orbittest-client run "My Collection" \
  --env ci \
  --reporter json,junit \
  --out ./reports

The JUnit report drops straight into most CI test dashboards, and the JSON report carries full request/response detail for custom processing. The runner exits with code 0 when every request and test passes and a non-zero code otherwise, so a failing run fails the build.

Use it in GitHub Actions

.github/workflows/api-tests.yml

name: API tests
on: [push]
jobs:
  api-tests:
    runs-on: windows-latest
    steps:
      - uses: actions/checkout@v4
      - name: Run Orbittest Client collection
        run: orbittest-client run "My Collection" --env ci --reporter junit --out reports
      - name: Publish results
        if: always()
        uses: actions/upload-artifact@v4
        with:
          name: api-test-reports
          path: reports

Note

Command and flag names above reflect v1.0.1. Run orbittest-client --help to see the authoritative list of commands and options for your installed version.

---

Upgrading

Orbittest Client updates automatically in the background, so most users are already on v1.0.1. To install or reinstall manually, download the signed Windows installer from the release page.

Download v1.0.1 Signed Windows installer on the GitHub releases page.

What is Orbittest Client? The overview — what it is, the full feature list, and how licensing works.

User Guide The full walkthrough — requests, environments, scripts, Ghost, and Insights.

Data-Driven Testing Drive a collection from a CSV or JSON file, one iteration per row.