Errors and limits
What the processor routes refuse, and how much one job may be.
Loading documentation…
Refusals follow the shape every Specter route uses — {"error": {"message": …}}, one sentence a
person can act on — see Errors.
| Status | When |
|---|---|
400 | The body is wrong — the message names the rule: no files, more than 25, a file with no name or size, an unknown documentType, a limit or before out of range. |
401 | No key (a board API key is required), or an unknown or revoked one (that key does not work here). |
402 | A key from Settings → Developer, on a workspace without the Enterprise plan. |
403 | The key lacks the scope — this key was not given processing — or is a board key, which can't process. |
404 | No job or deal with that id that this key can reach. |
409 | would_supersede: processing would replace fields a person entered by hand; the answer lists them in superseded. Send "replace": true to go ahead. |
429 | Too many requests on the /v1/ingest deal routes. Wait Retry-After seconds. |
503 | File storage isn't available; retry later. |
A file the processor couldn't read doesn't fail a request — it shows on the job: its line in
job.documents has outcome: "failed" and a reason.
| Limit | Value |
|---|---|
| Files per job | 25 |
| Upload URL | Works for 15 minutes |
| Jobs per list page | 1–200, default 50 |
Deal routes (/v1/ingest/rows/…) | 120 requests a minute per key, shared with the board routes |
Job routes (/v1/api/jobs) | No per-key rate limit |
Loading many deals? Start them one after another rather than all at once, and poll each at the pace in Read results.