Sections10
Reading time8 min
EvidenceWorking integration

POST /api/webhooks, POST /api/webhooks/:id/test

Document extraction webhooks tell your system when the work is done. Dynamite Docs sends an extraction.completed event to your endpoint, signs the raw body with HMAC-SHA256 and retries temporary failures. You can register up to five endpoints per account. No polling loop required.

When the completion event is sent

  • Scripts that poll for new extractions burn requests and lag by the poll interval. Nobody wants their document pipeline to be as stale as the last cron run.
  • An unauthenticated webhook is a spoofing hole. Anyone can POST a fake event, and a receiver that trusts it acts on data that never existed.
  • Transient failures (a 429, a 5xx, a network blip) should be retried, not dropped. A lost event is a silent data gap.
  • Webhook payloads that are not signed leave the receiver guessing whether the event is real.

How webhooks work

Dynamite Docs logoDynamite Docs
The handoff
Source document: A signed eventRegister an endpoint. Get the secret. Receive the event. Verify and retry. Illustrative example, not extracted customer data.FROM SOURCE FILE TO A RESULT YOU CAN USESourcedocumentReview workspaceA signedevent1Register anendpoint2Get the secret3Receive the event
  1. 01Register an endpoint
  2. 02Get the secret
  3. 03Receive the event
  4. 04Verify and retry
Send the result with a signature. Illustrative example.
01

Register an endpoint

Create a webhook with an HTTPS URL, up to five per account. Endpoints are validated as public URLs (SSRF-guarded) so the service never posts to internal addresses.

02

Get the secret

Your webhook secret is shown once at creation and used to verify signatures. You confirm the endpoint by its signature. Nothing is trusted on the URL alone.

03

Receive the event

When an extraction completes, we POST the extraction.completed payload with columns, rows, metadata, and confidence, signed in the X-Dynamite-Signature header.

04

Verify and retry

Verify the HMAC-SHA256 signature over the raw body before acting. Network errors, 429s, and 5xx retry with exponential backoff and jitter, up to three attempts.

Webhook payload and delivery

Dynamite Docs logoDynamite Docs
Inside the output
Source document: A signed eventEvent: extraction.completed. Endpoints: up to 5 per account. Signature: HMAC-SHA256 in X-Dynamite-Signature. Illustrative example, not extracted customer data.Extracted fieldsDOCUMENT SCHEMAeventextraction.completedendpointsup to 5 per accountsignatureHMAC-SHA256 in…A signed eventDESTINATION FIELDSEventMap to your destination schemaEndpointsMap to your destination schemaSignatureMap to your destination schemaIllustrative mapping. Confirm the field names accepted by your destination.
Event
extraction.completed
Endpoints
up to 5 per account
Signature
HMAC-SHA256 in X-Dynamite-Signature
Send the result with a signature. Illustrative example.

The webhook contract is short enough to verify:

Eventextraction.completed
Endpointsup to 5 per account
SignatureHMAC-SHA256 in X-Dynamite-Signature
Payloadcolumns, rows, metadata, confidence
Retriesbackoff + jitter, 3 attempts, 10s timeout
SSRF guardpublic URLs only, internal targets rejected
Test buttonPOST /api/webhooks/:id/test

A realistic example

The payload your endpoint receives and how to verify it:

FieldExamplePurpose
eventextraction.completedTells the receiver what happened
data.columns["Invoice #", "Date", "Total"]The table headers
data.rows[["INV-2041", "2026-06-03", "1240.00"]]The extracted rows
data.confidence0.97Average confidence of the extraction
X-Dynamite-Signaturehmac-sha256 hex digestProof the event is genuine

What webhooks do and do not

Does

  • POST extraction.completed events to your HTTPS endpoints with an HMAC-SHA256 signature over the raw body.
  • Retry transient failures (network, 429, 5xx) with exponential backoff and jitter, up to three attempts.
  • Reject non-public/internal target URLs to keep delivery SSRF-safe.

Does not

  • Does not send the full document bytes. Webhooks carry the extracted data, not the file.
  • Does not retry forever: three attempts max, so a broken endpoint cannot be hammered.
  • Does not deliver to endpoints that cannot verify the signature. Verification is the receiver’s job, and the secret is shown once.

Why webhooks complete the outbound story

Push beats poll. An event the moment extraction completes means your downstream systems act in real time, not on the last cron run.

HMAC signing makes delivery verifiable. The receiver can prove an event is genuine before trusting a single field.

Retries with backoff and an SSRF guard make the contract reliable and safe, so the webhook channel can be trusted for production traffic.

Setup and delivery questions

Extraction guides

Related integrations

Document workflows it feeds

From the blog

Get told when extraction finishes.

Register an endpoint, verify the signature, and let extraction.completed events trigger the next step in your stack.

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.