Background job status — Era documentation

Returns the status of a workflow run in the background, and its result once it finishes.

GEThttps://app.getera.io/api/jobs/{jobId}

API key

This is the statusUrl you get back when you send Run a workflow with X-Execution-Mode: async. Poll it every few seconds until the job finishes.

Authentication

An API key in the x-api-key header. The key's owner must have access to the workflow the job belongs to.

Path parameter

Name	Type	Required	Description
`jobId`	string	Yes	The `jobId` from the run response.

Example

curl https://app.getera.io/api/jobs/job_7f3c \
  -H "x-api-key: ERA_API_KEY"

Response

status is one of queued, processing, completed, failed.

While running:

{
  "success": true,
  "taskId": "job_7f3c",
  "status": "processing",
  "metadata": { "startedAt": "2026-10-14T09:30:00.000Z" },
  "estimatedDuration": 300000
}

Once finished:

{
  "success": true,
  "taskId": "job_7f3c",
  "status": "completed",
  "metadata": {
    "startedAt": "2026-10-14T09:30:00.000Z",
    "completedAt": "2026-10-14T09:30:04.500Z",
    "duration": 4500
  },
  "output": { "content": "Quote prepared." }
}

On failure you get status: "failed" and an error field.

Errors

Error bodies look like {"error": "...", "code": "..."}.

Status	When
`401`	Missing or invalid key.
`403`	You have no access to this job.
`404`	Job not found.
`500`	The status could not be read.