Connect without bypassing control.

01 · Getting started

Create a workspace API key.

1. Sign in as a workspace owner or admin.
2. Open Settings and find Developer API keys.
3. Create a key. The current v1 key grants the narrow read and change-request write permissions listed on this page.
4. Copy the key immediately. AgentHub stores its hash and cannot show it again.

02 · Authentication

Send the key as a bearer token.

Every v1 request uses the Authorization header. Keep the key on the server and never place it in client-side code, a public workflow export, or a prompt.

Authorization: Bearer ah_live_your_key

03 · Endpoints

The current public surface is intentionally small.

Use an optional ISO timestamp in since when polling change requests. The maximum limit is 100. Deduplicate results using the record id.

04 · Create a change request

File the request. Do not skip the lifecycle.

The client and workflow must already exist in the same AgentHub workspace. Title, request text, client ID, and workflow ID are required.

curl https://app.agenthub.ai/api/v1/change-requests \
  -H "Authorization: Bearer ah_live_your_key" \
  -H "Content-Type: application/json" \
  -d '{
    "client_id": "client-uuid",
    "workflow_id": "workflow-uuid",
    "title": "Update the lead routing rules",
    "request_text": "Route enterprise leads to the strategic accounts team.",
    "priority": "normal"
  }'

Allowed priorities are low, normal, high, and urgent.

Example response

{
  "id": "change-request-uuid",
  "client_id": "client-uuid",
  "workflow_id": "workflow-uuid",
  "title": "Update the lead routing rules",
  "request_text": "Route enterprise leads to the strategic accounts team.",
  "status": "requested",
  "priority": "normal",
  "requested_by_name": null,
  "due_at": null,
  "source": "agenthub",
  "source_reference": "AgentHub API: Zapier production",
  "created_at": "2026-07-29T14:35:00.000Z",
  "updated_at": "2026-07-29T14:35:00.000Z",
  "client_name": "Northwind Growth",
  "workflow_name": "Inbound qualification"
}

05 · API boundaries

What v1 does not expose.

• No client or workflow creation.
• No approval action.
• No live automation mutation or workflow write-back.
• No verification, completion, or client-brief sign-off.
• No general-purpose outbound webhooks yet.