Reference
Exact contracts — endpoints, error codes, event payloads, limits, cron, and environment.
Everything on these pages is a contract rather than advice. If a page here and a guide disagree, this section is correct.
HTTP API
API
Every /v1 endpoint, the scope it requires, and its response envelope.
Error codes
Status, code, meaning, and what to do — for every error the API returns.
Limits and quotas
Field bounds, execution limits, rate limits, and payload sizes in one table.
Events and execution
Webhooks
Headers, signature construction, payload schema, and retry policy.
Run states and error categories
The complete enums, with retryability.
Cron syntax
Accepted fields, examples, and timezone evaluation.
Operating
Environment variables
Every variable the API and UI read, with validation rules.
Deployment
Deploy the UI, API worker, docs, cron schedule, and database.
Conventions
Every successful response is an envelope:
{ "data": {}, "requestId": "01J..." }Every error is the matching shape:
{
"error": { "code": "validation_error", "message": "…", "details": {} },
"requestId": "01J..."
}requestId identifies the request in service logs — include it in any support
conversation. Two endpoints add a single extra top-level field, returned once
and never again: key when creating an API key, and webhookSecret when
setting a routine's webhook URL.