Skip to main content
The Infragrid REST API is the canonical interface behind the SDKs, CLI, and MCP adapter.
All public routes are versioned under /v1 and use JSON.

Authentication

Send a workspace API key as a bearer token:
The key determines the workspace and allowed scopes. API-key administration endpoints are the exception: they require an authenticated dashboard session.
API keys are server credentials. This reference uses copy-only request examples and does not submit live keys from the browser.

Resources

Browser runs

Start a free-form task or ordered workflow, recover status, list history, and cancel work.

Published Blueprints

Discover active definitions and start immutable published revisions.

Blueprint runs

Cursor-page API-triggered runs, poll safe snapshots, and cancel work.

API keys

Manage scoped workspace credentials through an authenticated dashboard session.

Request correlation

The gateway returns X-Request-ID when available. Include it with the run ID in support diagnostics. Never include the API key or website credentials.

Pagination

  • Browser runs use limit and offset.
  • Blueprint runs use limit and an opaque cursor.
  • Published Blueprints use a bounded limit.
  • List endpoints return at most 100 items.

Idempotent creation

POST /v1/runs and POST /v1/blueprints/{blueprint_id}/runs accept X-Idempotency-Key. A matching retry returns the stable original result; the same key with a different request body returns 409.

Run statuses

Browser runs: queued, running, completed, failed, cancelled. Blueprint runs can additionally report waiting_for_approval, paused, user_controlling, and interrupted.

Common error body

See Errors and retries for status-specific handling.
Last modified on August 16, 2026