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

# API reference

> Trigger workflows over HTTP today; the full read API is in development.

> [!NOTE]
>
> **Partial today.** You can already start a workflow over HTTP via an [API trigger](https://docs.celerflow.ai/concepts/triggers.md#api-trigger). The broader read API — fetching runs and listing workflows — is still in development, and its endpoint shapes and error formats may change.

## Available today: API triggers

Every deployed workflow can expose a single **API trigger** — an HTTP endpoint that starts a run:

```
POST /triggers/api/{triggerId}
Authorization: Bearer cfk_xxx
Content-Type: application/json

{ "payload": { ... } }
```

The `cfk_` key is created when you add an API trigger to a workflow. The request body is passed into the run as trigger context, which steps can bind to. See [Triggers](https://docs.celerflow.ai/concepts/triggers.md) for the full setup, plus webhook and schedule triggers.

## In development: the read API

When the read surface ships, you'll also be able to:

* Fetch the status and step output of a specific run.
* List workflows and their recent runs for a team.

These will use the same team-scoped `Authorization: Bearer <key>` scheme. If you'd like early access, let us know — see [Roadmap](https://docs.celerflow.ai/platform/roadmap.md).

## See also

* [Triggers](https://docs.celerflow.ai/concepts/triggers.md) — webhook, API, and schedule triggers you can use now.
* [Workflows](https://docs.celerflow.ai/concepts/workflows.md) — the lifecycle the API exposes.
* [Runs & executions](https://docs.celerflow.ai/concepts/runs.md) — what the run-fetch endpoints will return.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.