Sections10
Reading time8 min
EvidenceWorking integration

Answer in 30 seconds

Extract document data using LLMs through the Dynamite Docs REST API. Submit files, retrieve structured rows, and manage scoped keys within plan limits.

/api/v1/extractions, /api/v1/infer, /api/tokens

Put the document extraction API inside your product, CI job or internal tool. Create a scoped key, send it as Authorization: Bearer dd_live_<key> or X-API-Key, and POST the file to /api/v1/infer. The versioned API returns structured rows without a browser session, so your code can validate the response and decide what happens next.

A manual export button is not an API

  • If a person must click Export, every downstream job waits for that person.
  • Scripts need a stable credential with a narrow scope. A browser session cookie is the wrong tool.
  • The response needs predictable rows, metadata and errors that code can validate.
  • A token that can do everything becomes a long-lived liability once it lands in a codebase.

How the API works

Dynamite Docs logoDynamite Docs
The handoff
Source document: A structured API responseCreate a scoped key. Pull extractions from /api/v1. Or infer from a document. Feed it into your systems. Illustrative example, not extracted customer data.FROM SOURCE FILE TO A RESULT YOU CAN USESourcedocumentReview workspaceAstructuredAPI…1Create a scopedkey2Pull extractionsfrom /api/v13Or infer from adocument
  1. 01Create a scoped key
  2. 02Pull extractions from /api/v1
  3. 03Or infer from a document
  4. 04Feed it into your systems
A document request. Named fields back. Illustrative example.
01

Create a scoped key

From the app header under Webhooks & API (or /app?modal=webhooks), mint a scoped key. Keys look like dd_live_<64 hex>. The server stores only their SHA-256 hash, and the full secret is shown exactly once. Manage (list, revoke) them from the same panel.

02

Pull extractions from /api/v1 through Dynamite Docs

GET /api/v1/extractions lists your tables with pagination and filtering; GET /api/v1/extractions/:id/export?format=csv|json|xlsx returns one in the format your pipeline consumes. Send your key via the Authorization: Bearer <key> header or X-API-Key header.

03

Or infer from a document

POST /api/v1/infer uploads a document (multipart/form-data) and runs the same extraction engine as the app, returning the structured table in the response. It counts as one API call. Successful hosted pages and Free or Starter [BYOK pages draw](/integrations/connect-custom-llm-api-keys) from the monthly PE budget; Pro or Scale BYOK pages cost 0 PE. Extractions persist and trigger webhooks. The interactive POST /api/extract/infer remains for session-authenticated calls.

04

Feed it into your systems

The JSON shape drops straight into your pipeline: a procurement system ingesting invoice rows, a finance tool importing bank statement transactions. The shape is consistent, so one consumer handles every document type.

What the API exposes

Dynamite Docs logoDynamite Docs
Inside the output
Source document: A structured API responseScoped keys: hashed at rest, revocable, secret shown once. Authentication: Authorization: Bearer or X-API-Key. Versioned endpoints: GET /api/v1/extractions, GET :id/export, POST /api/v1/infer. Illustrative example, not extracted customer data.Extracted fieldsDOCUMENT SCHEMAscoped_keyshashed at rest, revocable, secre…authenticationAuthorization: Bearer or…versioned_endpointsGET /api/v1/extractions, GET…A structured API responseDESTINATION FIELDSScoped keysMap to your destination schemaAuthenticationMap to your destination schemaVersioned endpointsMap to your destination schemaIllustrative mapping. Confirm the field names accepted by your destination.
Scoped keys
hashed at rest, revocable, secret shown once
Authentication
Authorization: Bearer or X-API-Key
Versioned endpoints
GET /api/v1/extractions, GET :id/export, POST /api/v1/infer
A document request. Named fields back. Illustrative example.

The versioned API exposes the calls a document pipeline needs:

Scoped keyshashed at rest, revocable, secret shown once
AuthenticationAuthorization: Bearer or X-API-Key
Versioned endpointsGET /api/v1/extractions, GET :id/export, POST /api/v1/infer
Pagination & filterspage, limit, sort, order, doc_type
FormatsCSV (UTF-8 BOM), JSON, XLSX
InferencePOST /api/v1/infer (multipart upload)
Usage meteringGET /api/v1/usage (calls vs monthly limit)
Rate limiting60/min per key, 20/min inference

A realistic example

A two-call integration, start to finish:

CallPurposeReturns
POST /api/tokens (session auth)Create a scoped API keydd_live_<64 hex>, shown once
GET /api/v1/extractions/<id>/export?format=json (Bearer / X-API-Key)Pull an extraction with the key{ columns, rows, metadata, docType }

Request & response examples

Every versioned endpoint is key-authenticated and returns structured JSON or export formats. Send your API key in either the Authorization: Bearer dd_live_... header or the X-API-Key: dd_live_... header.

GET/api/v1/extractions/:id/export?format=json

Fetch structured tabular data and document metadata for any completed extraction.

Request (cURL)

GET /api/v1/extractions/:id/export?format=json
curl -X GET \
  -H "Authorization: Bearer dd_live_a8f92b7c4d1e0394..." \
  "https://app.dynamitedocs.com/api/v1/extractions/ext_01j5x9b3/export?format=json"

Response (200 OK)

200 OKStatus: 200 OK
{
  "id": "ext_01j5x9b3",
  "fileId": "file_8829f0",
  "fileName": "vendor_invoice_1092.pdf",
  "docType": "Invoice",
  "label": "August Operations",
  "columns": [
    "Invoice Number",
    "Date",
    "Vendor",
    "Description",
    "Line Total",
    "Tax",
    "Amount Due"
  ],
  "rows": [
    [
      "INV-1092",
      "2026-08-01",
      "Acme Industrial Ltd",
      "Precision CNC milling components",
      "$1,250.00",
      "$100.00",
      "$1,350.00"
    ]
  ],
  "metadata": {
    "vendor": "Acme Industrial Ltd",
    "invoice_number": "INV-1092",
    "total": "1350.00",
    "currency": "USD"
  },
  "confidence": 0.98,
  "fieldConfidence": {
    "Invoice Number": 0.99,
    "Amount Due": 0.98
  },
  "summary": "Vendor invoice from Acme Industrial Ltd totaling $1,350.00.",
  "createdAt": "2026-08-15T09:12:00.000Z"
}

What the API does and does not

Does

  • Provides key-authenticated access to extractions and export formats via versioned /api/v1 endpoints with Bearer or X-API-Key auth.
  • Stores keys as SHA-256 hashes only and shows the raw secret exactly once at creation.
  • Rate-limits per key and meters every call against the monthly allowance, with a usage endpoint.
  • Enforces hosted page caps and the monthly PE budget on standalone inference. BYOK on Free and Starter is metered; BYOK on Pro and Scale is unlimited.

Does not

  • Does not expose file, settings, account, or billing mutations. Those actions require your session.
  • Does not allow API traffic to bypass rate limits, the monthly call allowance, or the processing budget.
  • Does not store your key in plaintext anywhere on the server.

Why the API belongs in the baseline

A token-authenticated export turns every extraction into a stable data source for the systems you already run, no human in the loop, no session cookie in a script.

Read-only, hashed tokens are safe to embed in pipelines and vendor tools, which is the only kind of credential you should be committing to config.

Standalone inference gives you programmatic document reads with the same caps and budget as the app, so automation cannot quietly game the pricing model.

Setup and delivery questions

Extraction guides

Related integrations

Document workflows it feeds

From the blog

Put extraction behind your own API.

Create a scoped API key from the workspace (/app?modal=webhooks), then submit a document or pull reviewed rows into the system you run.

Can we save optional cookies?

Essential cookies keep you signed in. With your permission, optional analytics cookies and masked session replays help us understand usage and diagnose errors. Privacy policy. Change your choice anytime in Cookie settings.