Trigger job execution
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.
bearerAuthAuthorizationBearer <token>Project-scoped CLI token (sck_live_* or sck_test_*) for documented API operations that accept bearer authentication. Interactive browser operations may require a session cookie. Trigger keys (sck_trigger_* / legacy job_*) are accepted only by job trigger endpoints.
id*stringJob ID
uuidlocation?stringOptional 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.
Job triggered
application/json- response
success?booleanmessage?stringdata?curl -X POST 'https://demo.supercheck.dev/api/jobs/497f6eca-6276-4993-bfeb-53cbbbba6f08/trigger'{ "success": true, "message": "string", "data": { "jobId": "9d222c6d-893e-4e79-8201-3c9ca16a0f39", "jobName": "string", "runId": "78c33d18-170c-44d3-a227-b3194f134f73", "status": "queued", "position": 0, "testCount": 0, "triggeredBy": "string", "triggeredAt": "2019-08-24T14:15:22Z" }}