Skip to main content
GET
/
api
/
v1
/
external
/
status
/
{runId}
Get run status
curl --request GET \
  --url https://rts-builder.slayers.tech/api/v1/external/status/{runId} \
  --header 'X-API-Key: <api-key>'
{
  "error": "",
  "finished_at": "2026-03-29T02:33:41.139079Z",
  "run_id": "9bdeb4af-cab4-4de3-9f0f-758771d10991",
  "started_at": "2026-03-29T02:32:54.167691Z",
  "status": "completed",
  "steps": [
    {
      "id": "993af399-0e1a-456e-ba12-d465e7f9a5e6",
      "node_id": "tool-1",
      "tool": "crt",
      "status": "completed",
      "exit_code": 0
    }
  ]
}

​
Get run status

​
Status transitions

Observed values:
  • pending
  • running
  • completed
Internal run pages also account for failed and cancelled, and callers should handle those states as well.

Authorizations

​
X-API-Key
string
header
required

Team-scoped RTS Builder API key.

Path Parameters

​
runId
string<uuid>
required

Run UUID.

Example:

"9bdeb4af-cab4-4de3-9f0f-758771d10991"

Response

Run status retrieved successfully.

​
error
string
required

Empty string on success.

​
run_id
string<uuid>
required
​
status
enum<string>
required
Available options:
pending,
running,
completed,
failed,
cancelled
​
steps
object[]
required
​
finished_at
string<date-time> | null
​
started_at
string<date-time> | null