01 · Getting started

Create a workspace API key.

Sign in as a workspace owner or admin.
Open Settings and find Developer API keys.
Create a key. The current v1 key grants the narrow read and change-request write permissions listed on this page.
Copy the key immediately. AgentHub stores its hash and cannot show it again.
A key works only while the person who created it is an owner or admin. Removing that person, or changing their role, turns their keys off for good.

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

Test the connectionGET https://app.agenthub.ai/api/v1/auth/test

03 · Endpoints

Available endpoints

MethodEndpointPurpose

GET/api/v1/clientsList workspace clients.

GET/api/v1/workflows?client_id={id}List workflows, optionally filtered by client.

GET/api/v1/change-requests?limit=25Poll the newest change requests.

POST/api/v1/change-requestsCreate a requested change for an existing client workflow.

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

Create a change request

The client must be managed, and its 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.

Need an endpoint that is not listed?Send the use case through a product question. We will evaluate the operating need before widening write access.

06 · Connected workflow version history

History starts with a safe baseline.

The first supported sync for an n8n, Make, or Zapier workflow records a forward-only structural baseline. AgentHub does not reconstruct versions from before that baseline was recorded.

Later syncs can show changes to workflow name or state, steps, connected systems, order, schedule, and routing where the provider exposes those details.
The level of detail differs by provider. When safe structural data cannot explain a changed fingerprint, AgentHub says the details are unavailable.
Credentials, parameters, field values, and execution payloads are not stored in the structural snapshot.
Node and step names are treated as private workspace data.
Public API v1 does not expose workflow-version or diff endpoints.

Connect your tools to AgentHub.