Automate AI document extraction with APIs and webhooks
- API token
- The key-authenticated public API lives under /api/v1. A scoped key can list and export extractions, check usage, and submit a document for inference; file, settings, account, and billing changes still require a signed-in workspace session.
- Document request
- Export a completed extraction with GET /api/v1/extractions/:id/export?format=csv|json|xlsx, or submit a document with POST /api/v1/infer. Only the key's SHA-256 hash is stored.
Pull structured data into your own stack
How do you automate document extraction using the REST API and webhooks?
Use the /api/v1 endpoints to submit a document, retrieve an extraction, or download a result. Register a webhook when your system needs a signed extraction.completed notification.
The key-authenticated public API lives under /api/v1. A scoped key can list and export extractions, check usage, and submit a document for inference; file, settings, account, and billing changes still require a signed-in workspace session.
Export a completed extraction with GET /api/v1/extractions/:id/export?format=csv|json|xlsx, or submit a document with POST /api/v1/infer. Only the key's SHA-256 hash is stored.
Register up to 5 webhook endpoints per account; each extraction.completed POST carries an HMAC-SHA256 signature in the X-Dynamite-Signature header computed over the raw body.
Webhook deliveries retry with exponential backoff and jitter on network errors, 429s, and 5xx. Up to 3 attempts with a 10-second timeout.
Connect Google Sheets once and push any extraction with one click. A fresh tab per push, plus a Document Fields tab for metadata.
The REST API authenticates requests via SHA-256 hashed API tokens, while outbound webhooks deliver payload notifications with HMAC-SHA256 signatures across 3 retry attempts.
Related workflows and guides
- Read endpoint specifications, authentication patterns, and cURL snippets in the REST API integration overview.
- Configure custom LLM endpoints and BYOK credentials in AI keys and provider setup.
- Review API token hashing and payload encryption practices in security and encryption standards.
Open the document extraction app, browse document input and export integrations, or compare PE, storage, and API limits.
- 01API token
- 02Document request
- 03Signed webhook
- API token
- The key-authenticated public API lives under /api/v1. A scoped key can list and export extractions, check usage, and submit a document for inference; file, settings, account, and billing changes still require a signed-in workspace session.
- Document request
- Export a completed extraction with GET /api/v1/extractions/:id/export?format=csv|json|xlsx, or submit a document with POST /api/v1/infer. Only the key's SHA-256 hash is stored.
- Signed webhook
- Register up to 5 webhook endpoints per account; each extraction.completed POST carries an HMAC-SHA256 signature in the X-Dynamite-Signature header computed over the raw body.