> ## Documentation Index
> Fetch the complete documentation index at: https://docs.testorim.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Cancel every run in a batch

> Same as the single-run cancel, applied to every `pending`/`running` row sharing the `batchId`. This is the way to stop a whole fuzz batch or matrix fan-out. Ownership is checked by requiring at least one run in the batch to belong to the key's organization. Takes no request body.



## OpenAPI

````yaml /api-reference/openapi.yaml post /api/runs/batch/{batchId}/cancel
openapi: 3.1.0
info:
  title: Testorim API
  version: 1.0.0
  summary: AI browser QA. Trigger and inspect test runs from CI or your terminal.
  description: >
    Testorim runs plain-English browser QA tests in a real Playwright browser.

    This document describes the **API-key-authenticated subset** of the HTTP

    API, meaning the endpoints a CI pipeline, a terminal, or a third-party

    integration is expected to call.


    ## Scope and honesty notes


    * **This is not a frozen contract.** `1.0.0` is a documentation version,
      not a server version. The API is **unversioned in the URL**. There is
      no `/v1` prefix; every router mounts flat under `/api`.
    * **This is a subset.** The app's own SPA calls many more endpoints
      (billing, Polar/Clerk/GitHub webhooks, Slack and GitHub OAuth
      callbacks, fixtures, environments, schedules, alerts, visual
      baselines, run sharing, flakiness, test-data variables, perf budgets,
      role probes, bug reports, org/invite management). Those are
      deliberately **not** documented here: they are either session-oriented,
      provider-signed, or not stable enough to hand to an integrator.
      `PATCH`/`DELETE` on projects and procedures also exist in the code but
      are out of scope for this reference.

    ## Authentication


    Send the API key as an **HTTP Bearer token**:


    ```

    Authorization: Bearer tst_live_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

    ```


    Testorim reads exactly one header, `Authorization`, and accepts either

    credential on it:


    1. a value matching `tst_live_…` (prefix + at least 16 more chars) is
       verified as an API key by SHA-256 hash lookup, or
    2. anything else is verified as a Clerk session JWT (the browser path).


    An API key is bound to **one user and one organization**. On every

    request the middleware pins `currentOrg` to the key's org, so a key

    issued for org A can never read or write org B, even when the owning

    user belongs to both. If the user has since been removed from that org,

    the key stops working (`401`).


    Every list and lookup is org-scoped. A resource belonging to another

    organization returns `404`, never `403`, so the API does not leak the

    existence of rows you cannot see.


    ## Role restrictions


    Members of an org with role `viewer` are read-only: any

    non-`GET`/`HEAD`/`OPTIONS` request is rejected with `403` and

    `code: "read_only_role"`. This applies to API-key callers too, because

    the key inherits the user's role in the bound org.


    ## Rate limiting


    Limits are enforced as a sliding window:


    | Limiter | Policy | Keyed by | Applied to |

    | --- | --- | --- | --- |

    | `api:global` | 600 / minute | client IP | every `/api/*` request |

    | `procedure:minute` | 30 / minute | authenticated user id | `POST
    /api/runs/trigger` |

    | `api:read` | 120 / minute | authenticated user id | `GET /api/runs/active`
    |

    | `auth:strict` | 5 / 15 minutes | client IP | **failed** credential checks
    |


    A throttled request returns `429`, a JSON body of

    `{ "error": …, "retryAfter": <seconds> }`, and a `Retry-After` response

    header. **There are no `X-RateLimit-*` headers**. The middleware sets

    only `Retry-After`, so do not write a client that depends on quota

    headers.


    Rate limits are separate from **plan quotas**. Exhausting the

    organization's monthly run allowance also returns `429`, but from

    `checkRunLimit` rather than the limiter, and with no `Retry-After`.


    ## Request body rules


    * JSON bodies are capped at **1 MB**.

    * Any string anywhere in the body containing a NUL byte (`U+0000`)
      rejects the whole request with `400` before it reaches a handler.
    * Bodies are validated with Zod. A schema failure returns `400` with
      `{ "error": "Invalid request body", "issues": [...] }`, where `issues`
      is the raw `ZodError.issues` array.
  contact:
    name: Testorim support
    email: info@fulgic.com
    url: https://testorim.com
  license:
    name: Proprietary
    identifier: LicenseRef-Proprietary
servers:
  - url: https://app.testorim.com
    description: >-
      Production. Single-origin deployment: Caddy on one GCP VM serves the SPA
      at `/` and reverse-proxies `/api/*` and `/ws` to the backend. This is also
      the default API base URL used by the Testorim CLI.
  - url: http://localhost:3001
    description: >-
      A locally running Testorim backend, for self-hosted or development use.
      The default port is 3001.
security:
  - ApiKeyAuth: []
tags:
  - name: Runs
    description: >-
      Trigger a test run and read its result. `POST /api/runs/trigger` is the
      endpoint CI actually uses.
  - name: Procedures
    description: Saved, replayable test sequences belonging to a project.
  - name: Projects
    description: A website-under-test, scoped to an organization.
  - name: API keys
    description: >-
      Mint, list and revoke API keys. Creating a key requires a browser session.
      See the operation notes.
  - name: Identity
    description: Who the presented credential belongs to.
paths:
  /api/runs/batch/{batchId}/cancel:
    post:
      tags:
        - Runs
      summary: Cancel every run in a batch
      description: >-
        Same as the single-run cancel, applied to every `pending`/`running` row
        sharing the `batchId`. This is the way to stop a whole fuzz batch or
        matrix fan-out. Ownership is checked by requiring at least one run in
        the batch to belong to the key's organization. Takes no request body.
      operationId: cancelRunBatch
      parameters:
        - name: batchId
          in: path
          required: true
          description: >-
            The batch identifier. Read it from a run's `batchId`, or from an
            active-run group. Not validated as a UUID by the handler, though the
            column is `uuid`.
          schema:
            type: string
      responses:
        '200':
          description: Cancellation processed for the batch.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/CancelResult'
        '401':
          $ref: '#/components/responses/Unauthorized'
        '403':
          $ref: '#/components/responses/ReadOnlyRole'
        '404':
          description: No run in this batch belongs to the key's organization.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
              example:
                error: Batch not found
        '429':
          $ref: '#/components/responses/RateLimited'
      security:
        - ApiKeyAuth: []
components:
  schemas:
    CancelResult:
      type: object
      title: CancelResult
      required:
        - cancelled
        - reapedHandlers
      properties:
        cancelled:
          type: integer
          minimum: 0
          description: >-
            Number of DB rows flipped from `pending`/`running` to `cancelled`.
            Zero when the run(s) had already finished.
        reapedHandlers:
          type: integer
          minimum: 0
          description: >-
            Number of live orchestrators whose in-memory cancel handler actually
            fired and tore a browser down. Can be lower than `cancelled` when a
            process already exited.
    Error:
      type: object
      title: Error
      description: >-
        The universal error envelope. Every failing handler in this surface
        responds with a JSON object carrying a human-readable `error` string;
        some add extra fields (see the other error schemas).
      required:
        - error
      properties:
        error:
          type: string
          description: Human-readable message. Not a stable machine-readable code.
      additionalProperties: true
    ReadOnlyRoleError:
      type: object
      title: ReadOnlyRoleError
      description: The one error in this surface with a stable machine-readable code.
      required:
        - error
        - code
      properties:
        error:
          type: string
          const: Viewers have read-only access to this workspace
        code:
          type: string
          const: read_only_role
    RateLimitError:
      type: object
      title: RateLimitError
      description: Emitted by the rate-limit middleware alongside a `Retry-After` header.
      required:
        - error
      properties:
        error:
          type: string
          description: The limiter's reason, e.g. `Rate limit exceeded. Try again in 42s.`
        retryAfter:
          type:
            - integer
            - 'null'
          description: >-
            Seconds until the window frees. Mirrors `Retry-After`. May be
            absent/null when the limiter did not report a reset time, in which
            case the header defaults to 60.
      additionalProperties: true
  responses:
    Unauthorized:
      description: |
        No `Authorization: Bearer …` header, or the credential did not
        verify. Distinct messages the code can return:

        * `Missing or invalid Authorization header`
        * `Invalid or revoked API key`
        * `API key owner not found`
        * `API key's organization is no longer accessible`. The key's user
          has been removed from the org it is bound to
        * `Invalid token` / `Token missing sub claim`. Clerk JWT path

        Repeated failures burn the `auth:strict` bucket (5 per 15 minutes
        per IP) and then return `429` instead.
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Error'
          example:
            error: Invalid or revoked API key
    ReadOnlyRole:
      description: >-
        The credential's user has the `viewer` role in the bound organization,
        and viewers may not make mutating requests.
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/ReadOnlyRoleError'
    RateLimited:
      description: >-
        Throttled. Every `/api/*` route sits behind `api:global` (600 / minute
        per IP); some routes add a tighter per-user limiter.
      headers:
        Retry-After:
          description: Seconds until the window frees up.
          schema:
            type: integer
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/RateLimitError'
  securitySchemes:
    ApiKeyAuth:
      type: http
      scheme: bearer
      bearerFormat: tst_live_<32 url-safe base64 chars>
      description: |
        Send `Authorization: Bearer tst_live_…`.

        Format (`services/api-keys.ts`): the literal prefix `tst_live_`
        followed by 24 random bytes rendered as 32 base64url characters.
        Only the SHA-256 hash is stored server-side. The shape check that
        routes a token down the API-key path rather than the Clerk JWT path
        requires the `tst_live_` prefix and a total length of at least 25
        characters.

        Keys are minted in the dashboard at `/settings/team`. The same header
        also accepts a Clerk session JWT, which is how the web app
        authenticates, but the JWT path is out of scope for this document.

````

## Related topics

- [Browser runs](/test-execution/browser-runs.md)
- [Platform overview](/developers/platform-overview.md)
- [Core capabilities](/introduction/core-capabilities.md)
- [Run and inspect a test](/getting-started/run-and-inspect.md)
- [Cancel a single run](/api-reference/runs/cancel-a-single-run.md)
