API Reference
The dOCR REST API — base URL, authentication, errors, and endpoints.
The dOCR REST API lets you extract structured data and manage resources programmatically. Reference pages below are generated from our OpenAPI specification.
Base URL
https://app.docr.dev/api/v1Authentication
All endpoints require an API key as a Bearer token. See Authentication.
Authorization: Bearer docr_sk_xxxxxxxxxxxxxxxxxxxxxxxxErrors
dOCR uses conventional HTTP status codes. Error responses share a simple shape:
{ "error": "A human-readable message" }| Status | Meaning |
|---|---|
400 | Malformed request (e.g. missing file or wrong content type). |
401 | Missing or invalid API key (or, for signed renders, an invalid signature). |
402 | Monthly credit allowance exhausted. Upgrade your plan. |
403 | Request IP is not whitelisted. |
404 | Resource not found. |
422 | Input failed validation (unsupported type, too large, too many pages, or invalid options). |
Endpoints
Extractions
Create, list, and retrieve extractions.
Screenshots
Render a URL or HTML to an image or PDF.
Captures
A unified view of every screenshot and upload.
Document Types
List the document types available to your organization.
OpenAPI spec
The machine-readable spec is available at
/openapi.yaml for generating clients and importing into tools
like Postman or Insomnia.
Webhooks
Receive signed events when extractions complete or fail.
Extract data from a document
Upload a single document and receive structured data. The request is processed synchronously and the completed extraction is returned. Accepted file types: `.pdf`, `.jpg`, `.jpeg`, `.png`, `.bmp`, `.webp`, `.docx`. Limits: 10 MB and 15 pages per document.