Skip to main content
Base URL:
Workspace resources live under /api/workspaces/{workspaceId}/…. Find your workspace id with ait workspaces or the list_workspaces MCP tool.

​
Authentication

Send an API key as a bearer token on every request:
Three layers bound what a request can do:
  1. Scopes — the key must hold a scope covering the endpoint (tasks:read, tasks:write, …). A * key holds them all. Missing scope → 403.
  2. Workspace role — the key acts as its owner, so the owner’s role applies: approve/reject/publish need Reviewer, task deletion and automation management need Admin. See Team & roles.
  3. Workspace binding — a key created for one workspace is rejected with 403 on any other.

​
Responses and errors

Success responses return the resource directly — object endpoints return a bare JSON object, list endpoints return either a bare array (tasks) or a cursor envelope (automations); each endpoint page notes which. Errors are:
Validation failures add a details array of field-level issues. Every response carries an x-request-id header — include it when reporting a problem.

​
Endpoints

Tasks

Create, list, approve, reject, publish.

Automations

Scheduled standing briefs.

RSS & podcast feeds

Hosted feeds and their public URLs.

MCP tools

The full 38-tool MCP catalog.