DEVELOPERS

A REST API for document extraction.

Post a document, get back structured JSON — authenticated with a scoped key, wired into your stack with signed webhooks.

Read the docs

Start free

A dark code panel showing a Bearer-authenticated request and JSON response.

AUTHENTICATION

Authenticate and extract in one call.

Every request is authenticated with a scoped key as `Authorization: Bearer docr_sk_…`. Post a document and dOCR returns structured JSON.

cURL

curl https://api.docr.dev/v1/extractions \
-H "Authorization: Bearer docr_sk_live_…" \
-F "file=@invoice.pdf" \
-F "type=invoice" \
-F "model=claude-opus-4-8"

Node

Python

RESPONSE

Typed, predictable output.

Every extraction returns the same envelope — an id, the document type, a status, and a data object whose fields match the type you requested. Example Invoice response:

{
"id": "ext_8f2a…",
"type": "invoice",
"status": "completed",
"model": "claude-opus-4-8",
"data": {
"invoice_number": "INV-2042",
"currency": "USD",
"total": "1284.00"
}
}

MODEL SELECTION

Pick your model per request.

Set `model` on each request to trade quality for speed without changing anything else in your integration.

Quality · claude-opus-4-8

Highest-quality extraction for dense or messy documents.

-F "model=claude-opus-4-8"

Speed · gemini-3-flash

A signed webhook header and HMAC verification snippet.

WEBHOOKS

Get notified the moment a job finishes.

Subscribe to extraction.completed and extraction.failed. Every delivery carries X-docr-Signature: t=…,v1=… — an HMAC-SHA256 of the timestamp and raw body, keyed with your webhook secret — and retries on failure. Verify before you trust:

const signed = t + "." + rawBody;
const expected = hmacSHA256(secret, signed);
assert(timingSafeEqual(expected, v1));