Skip to main content
Sandbox keys (ck_sandbox_...) exercise the entire API surface — the same endpoints, request shapes, status codes, and webhook events as live — with two differences:
  • Results are instant fixtures. Extractions complete immediately with realistic example output for the document type, so you can build against the real result shapes without waiting.
  • Nothing is billed. Sandbox activity never touches your usage pool.

Example documents

Sandbox ships with reference documents whose real extracted output is available to every sandbox key. Register a document under one of the filenames below (any byte_size works — no file upload is needed in sandbox) and extract it: the result is the actual output our engine produced for that document, so you can build against realistic field coverage, row counts, and validation results — not just the minimal generic fixture.
The filename match is case-insensitive and the declared_type must match the example’s type; any other filename returns the generic fixture for the declared type.

What to build against sandbox

  • The full upload → extract → result flow, including polling or webhook handling.
  • Error handling: invalid documents, missing scopes, idempotency replays.
  • Webhook signature verification — sandbox events are signed exactly like live events.

Differences to expect in live

  • Live extractions take minutes, not milliseconds — build your polling or webhook flow accordingly.
  • Live results reflect your actual documents; field coverage varies with document quality and layout.
  • Live extractions debit the pool at acceptance and refund automatically if processing fails.