Jobs

Trigger job execution

Changed on

Trigger a job run using a job-scoped trigger key in the Authorization: Bearer <trigger-key> header. For k6 jobs, an optional location query parameter can target an enabled location code or global for unrestricted any-worker routing. Note: this endpoint only accepts a job trigger key (sck_trigger_* / legacy job_*) in the Authorization header. CLI tokens (sck_live_*) are rejected with 401.

post/api/jobs/{id}/trigger

Request

  • Base URL
    https://demo.supercheck.dev
  • Auth
    HTTP bearer

Query parameters

locationstring

Optional execution location for k6 jobs. Use an enabled location code (for example us-east) or global for unrestricted any-worker routing. global is rejected when project location restrictions are enabled.

Response

Job triggered

successboolean
messagestring

Changes

    • warning

      removed the optional property from the response with the status

    • info

      added the new optional query request parameter location

    • info

      added the non-success response with the status

    • info

      added the non-success response with the status

    • info

      added the non-success response with the status

    • info

      added the optional property to the response with the status

    • info

      added the optional property to the response with the status

    • warning

      deleted the query request parameter location

    • warning

      removed the optional property from the response with the status

    • warning

      removed the optional property from the response with the status

    • info

      removed the non-success response with the status

    • info

      removed the non-success response with the status

    • info

      removed the non-success response with the status

    • info

      added the optional property to the response with the status