Launches API

The Launches API lets you list and read launches, and export one as a CTRF report, in a Qualflare project over REST at https://api.qualflare.com/api/v1/launches, authenticated with a project access token.

The three endpoints, each with its own section below:

List launches

List launches returns one page of the project's launches, newest first unless you sort them.

GET /api/v1/launches

Needs a project access token whose creator has the Viewer role or higher in the project.

curl -sS "https://api.qualflare.com/api/v1/launches?environments=staging" \
  -H "Authorization: Bearer $QF_TOKEN"

Returns 200: A page of launches: items and paging, 10 launches per page.

• Filters combine: platforms, automation, environments and languages can repeat; q searches the branch.

Get a launch

Get a launch returns one launch by its number, with its result counts.

GET /api/v1/launch/{launchSeq}

Needs a project access token whose creator has the Viewer role or higher in the project.

curl -sS "https://api.qualflare.com/api/v1/launch/88" \
  -H "Authorization: Bearer $QF_TOKEN"

Returns 200: The launch.

{
  "seq": 88,
  "framework": "playwright",
  "platform": "web",
  "os": "linux",
  "branch": "main",
  "commit": "4f2c9a1e7b3d",
  "status": "failed",
  "automation": "automated",
  "totalCount": 120,
  "passedCount": 112,
  "failedCount": 5,
  "errorCount": 0,
  "skippedCount": 3,
  "timeoutCount": 0,
  "abortedCount": 0,
  "flakyCount": 2,
  "retryCount": 4,
  "properties": {
    "build": "1432"
  },
  "environmentId": 3,
  "environmentName": "Staging",
  "languageName": "English",
  "languageUid": "en",
  "milestoneSeq": 3,
  "milestoneName": "v2.4 release",
  "browser": "chromium",
  "metadata": {
    "version": "0.4.0",
    "timestamp": "2026-10-28T09:12:31Z",
    "cliName": "qf"
  },
  "aiSummary": "Five checkout tests failed on the coupon step; the rest passed.",
  "aiSummaryStatus": "completed",
  "createdAt": "2026-10-28T09:12:33Z",
  "updatedAt": "2026-10-28T09:14:02Z"
}

• A number that isn't a launch of the project answers 404 with launch not found.

Export a launch as CTRF

Export a launch as CTRF returns one launch as a CTRF JSON report, with the same token access as reading the launch.

GET /api/v1/launch/{launchSeq}/ctrf

Needs a project access token whose creator has the Viewer role or higher in the project.

curl -sS "https://api.qualflare.com/api/v1/launch/88/ctrf" \
  -H "Authorization: Bearer $QF_TOKEN"

Returns 200: The launch as a CTRF JSON document.

• error, timeout and aborted are written as failed, with the exact status in the result's rawStatus (or in its extra as qualflare.status, when the upload sent its own rawStatus), so uploading the export again to POST /api/v1/collect/ctrf restores them.
• A launch with 20,000 or more case results (or 200,000 steps, 50,000 retry attempts or 20,000 attachments) answers 400 with launch is too large to export as a single CTRF document.
• Public report URLs don't offer the export.

See Send CTRF reports.

Launch fields

Every launch the Launches API returns has these fields:

CLI and MCP equivalents

The qf CLI and the MCP server run the same reads, so they return the same JSON:

Related

• Guides: Launches · Share and export results
• Reference: Upload results with the API · Errors and status codes
• CLI/API: Qualflare API