1. Documentation
  2. Processor
  3. Errors and limits
Open Specter
  • Introduction
  • Quickstart
  • Authentication
  • Errors
  • Rate limits
  • Best practices
  • Overview
  • Access
  • Best practices
  • Create a key
  • Read and write
  • Overview
  • Best practices
  • Hosted page
  • Submit from your code
  • Drafts, files and corrections
  • Overview
  • Best practices
  • Create a key
  • Send documents
  • Read results
  • Findings
  • Process a deal
  • Errors and limits

Errors and limits

What the processor routes refuse, and how much one job may be.

Loading documentation…

Process a deal< Previous

On this page

Limits

Refusals follow the shape every Specter route uses — {"error": {"message": …}}, one sentence a person can act on — see Errors.

StatusWhen
400The 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.
401No key (a board API key is required), or an unknown or revoked one (that key does not work here).
402A key from Settings → Developer, on a workspace without the Enterprise plan.
403The key lacks the scope — this key was not given processing — or is a board key, which can't process.
404No job or deal with that id that this key can reach.
409would_supersede: processing would replace fields a person entered by hand; the answer lists them in superseded. Send "replace": true to go ahead.
429Too many requests on the /v1/ingest deal routes. Wait Retry-After seconds.
503File 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.

Limits

LimitValue
Files per job25
Upload URLWorks for 15 minutes
Jobs per list page1–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.