Limits
How many requests a workspace can make each minute, the other limits your plan sets, and how to tell when you're close to them.
Requests per minute
Each workspace can make a set number of API requests per minute, shared by all of its keys:
| Plan | Requests per minute |
|---|---|
| Free | 5 |
| Builder | 50 |
| Pro | 200 |
| Enterprise | Custom |
Every response says where you stand:
| Header | What it holds |
|---|---|
X-RateLimit-Limit | Requests allowed per minute |
X-RateLimit-Remaining | Requests left in the current window |
X-RateLimit-Reset | Seconds until the window resets |
Over the limit, the API returns 429 Too Many Requests with a Retry-After header saying how many seconds to wait. See Retry safely.
Runs in progress at once
Your plan also limits how many runs can be in progress at the same time, listed as Workflows running at once on the pricing page. Starting a run while you're at the limit returns 429 with the code concurrency_limit. It has no Retry-After, since waiting a moment doesn't help: start the run once one of the others finishes.
Runs per month
Each run you start through the API counts as one of your plan's monthly runs, the same as a run started any other way. When the month's runs are used up, starting a run returns 429 with the code monthly_run_limit, and its resets_at says when runs come back: the 1st (UTC), unless you add runs or turn on extra runs in Billing first. See What counts as a run.
Request size
The body of a Run a workflow request can be at most 500 KB.
Keys per workspace
| Plan | API keys |
|---|---|
| Free | 1 |
| Builder | 10 |
| Pro | 40 |
| Enterprise | Custom |
Pricing always has the current figures for every plan.
Errors and retries
The error codes the API returns and what to do about each, the request ID to quote to support, which requests are safe to retry, and how idempotency keys stop a retry from starting a run twice.
Workflows
List the workspace's workflows, read one with its steps, or delete one for good.