Jobs

Get a job

GET /v1/jobs/{id} — requires content:read. Every job today corresponds 1:1 to a content row (there’s no separate async job type yet for automations or schedules).

{
  "data": {
    "id": "content_x1y2z3",
    "status": "ready",
    "resourceType": "content",
    "resourceId": "content_x1y2z3",
    "cost": 1,
    "error": null
  }
}

status is one of "queued", "running", "ready", "failed". In practice, POST /v1/content for type: "slideshow" resolves synchronously within the request — this endpoint exists for a consistent contract across content types and for future async pipelines, not because slideshow generation itself needs polling today.

⌘I

Getting Started

Guides

API Reference

Get a job

​Get a job

Get a job