Skip to main content
The AgentRuntime public API is served by the BFF at https://api.agentruntime.io. All customer integrations should use this base URL. For request/response samples, see API examples.

Interactive explorer

Browse a subset of workflow and run endpoints in the marketing site’s Scalar UI: agentruntime.io/api-reference
The marketing OpenAPI spec covers core workflow surfaces. It may lag behind the full BFF route catalog. Cross-check with the tables below or test against api.agentruntime.io.

OpenAPI specifications

Formal OpenAPI 3.1 specs exist for a subset of the API surface, including billing (/v1/billing/*) and onboarding (/v1/onboarding/*, /v1/setup/*) endpoints. There is no single full OpenAPI file covering every route today — use this page, API examples, and the interactive explorer above for the rest of the surface.

Authentication

All authenticated requests use either:
  • Session cookie — Browser sessions from the Console
  • Bearer PATAuthorization: Bearer pat_... for programmatic access
Scoped requests also require:
See API authentication. Role shorthand in tables: viewer+ = project_viewer or higher, contributor+ = project_contributor or higher, tenant_admin = workspace billing admin.

Workflows

Base path: /v1/workflows

Start, pause, resume, stop

POST /v1/workflows/{id}/command
params become workflow input ({{input.*}} in steps). See Run setup.

Runs and human tasks

Complete task body:
The human task step result always includes approved. The Console Approve/Reject buttons send only { "approved": true|false }. See Human tasks.

Run event types

Persisted on GET /v1/workflows/{id}/runs/{runID}/events. See also Runs and Command Center — Failure handling. Skip reasons on step_completed when skipped: true: Cancelled step (step_cancelled): data.cancelled: true, data.reason: "run_failed", optional caused_by_step_id. See Runs and Command Center — Failure handling for Console badges.

Inbound webhooks

Create subscription:
Response includes ingress_url, signing_secret (once), and subscription. Ingress request headers:
  • Authorization: Bearer pat_…
  • X-Agentruntime-Signature: sha256=<hmac-sha256 of raw body>
  • Content-Type: application/json
See Inbound webhooks.

Connections

Base path: /v1/connectionsproject_contributor

Google OAuth

WhatsApp


MCP

Base path: /v1/mcpproject_contributor unless noted.

Servers and catalog

Instances and config profiles

Duplicate connection CRUD also exists under /v1/mcp/connections for legacy clients.

AI, chat, and memory

Memory (preview)

Memory routes require memory kernel configuration. Console Memory UI may be off in production — see Feature availability.

Billing endpoints

Base path: /v1/billing GET /v1/config/stripe — publishable Stripe config for Console checkout. GET /v1/billing/plans returns tiers scoped to your workspace’s product (AgentRuntime Console → agentruntime). Catalog rows are keyed by (product_code, plan_code); the public response surfaces plan_code and pricing fields. See Multi-product billing. See Billing and credits and API examples.

Agents

Base path: /v1/agentsproject_viewer (read), project_contributor (write). Requires enableAgents in your deployment.

Analytics

Base path: /v1/analyticsproject_contributor Query window=month|week|all or bounded from / to with optional granularity on timeseries endpoints. See Analytics.

Personal access tokens

Console Settings → API keys manages the same keys for inbound webhook automation.

Error codes


SDKs and collections

Contact support@agentruntime.io for enterprise API SLAs.