Using Webhooks
Send extracted data to other systems via webhooks
Using Webhooks
Webhooks let you send extracted data to your own URLs when a document is processed. You add one or more webhook endpoint URLs in Integrations. DigiParser then POSTs the data to those URLs in JSON format. Use this to feed your own apps, databases, or workflows.
Where to set it up
- Open your parser and go to Settings → Integrations.
- Under Available Integrations, click Webhook.
- It appears under Added Integrations. Expand it to add and configure endpoints.
How to configure
Add endpoints
- Click Add Your First Endpoint (or Add another endpoint if you already have some).
- Enter the URL that should receive the data (e.g.
https://your-server.com/webhook). Use HTTPS when you can. - You can give each endpoint an optional name (e.g. “Production server”) so you can tell them apart in the list.
You can add multiple endpoints. Each processed document is sent to all of them.
Save
Click Save Changes. From then on, when a document is processed, the extracted data is sent to each endpoint as a JSON payload.
What is sent
DigiParser sends a JSON payload to your URL. It includes the extracted data (your parser fields and tables), plus metadata such as document id, name, url, and timestamp. The exact shape depends on your parser schema; you can inspect a sample request to see the format.
When data is sent
Data is sent when a document is processed (after extraction).
If you use Reviews & Approvals and a reviewer is assigned, webhooks wait until the document is approved. If no reviewer is assigned, webhooks are sent immediately after processing.
Tips
- Your endpoint should respond quickly (e.g. 200 OK). If you need to do slow work, save the payload and process it later.
- Use HTTPS and ensure your server is reachable from the internet so DigiParser can deliver.
- Use multiple endpoints to send the same data to different systems (e.g. your app and a logging service).
Verifying webhooks
Every webhook request is sent through our provider (Svix) and includes headers you can use to make sure the request is genuine:
svix-id– unique message identifiersvix-timestamp– when the message was createdsvix-signature– HMAC signature of the request body
On your server you can use the signing secret (shown next to each endpoint in the Webhook export settings) together with these headers to verify that:
- the request really came from DigiParser, and
- the payload was not modified in transit.
See How to verify webhooks for a short step‑by‑step guide and code examples you can hand to a developer.
Troubleshooting
- No data received – Check the URL is correct, uses HTTPS if required, and is publicly reachable. Check your server logs for incoming requests.
- Errors or timeouts – Your server may be slow or returning errors. Respond with 200 as soon as you’ve accepted the payload.
Next steps
- Integrations Overview – Other import and export options
- API Access – Use the Process API
- Setting Up Zapier – Connect 1000+ apps via Zapier
How is this guide?