> ## Documentation Index
> Fetch the complete documentation index at: https://docs.infragrid.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# API overview

> Authenticate, create durable runs, and work with the complete Infragrid v1 REST API.

The Infragrid REST API is the canonical interface behind the SDKs, CLI, and MCP adapter.

```text theme={null}
https://api.infragrid.ai
```

All public routes are versioned under `/v1` and use JSON.

## Authentication

Send a workspace API key as a bearer token:

```http theme={null}
Authorization: Bearer ig_live_...
Content-Type: application/json
```

The key determines the workspace and allowed scopes. API-key administration endpoints are the exception: they require an authenticated dashboard session.

<Warning>
  API keys are server credentials. This reference uses copy-only request examples and does not submit live keys from the browser.
</Warning>

## Resources

<CardGroup cols={2}>
  <Card title="Browser runs" icon="browser" href="/reference/runs/create">
    Start a free-form task or ordered workflow, recover status, list history, and cancel work.
  </Card>

  <Card title="Published Blueprints" icon="bolt" href="/reference/blueprints/list">
    Discover active definitions and start immutable published revisions.
  </Card>

  <Card title="Blueprint runs" icon="list-check" href="/reference/blueprint-runs/list">
    Cursor-page API-triggered runs, poll safe snapshots, and cancel work.
  </Card>

  <Card title="API keys" icon="key" href="/reference/api-keys/list">
    Manage scoped workspace credentials through an authenticated dashboard session.
  </Card>
</CardGroup>

## 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

```json theme={null}
{
  "detail": "Display-safe error message"
}
```

See [Errors and retries](/production/errors-retries) for status-specific handling.


## Related topics

- [Infragrid overview](/overview.md)
- [List API keys](/reference/api-keys/list.md)
- [Revoke an API key](/reference/api-keys/revoke.md)
- [Create an API key](/reference/api-keys/create.md)
- [Rotate an API key](/reference/api-keys/rotate.md)