Webhooks

The webhook destination sends extracted document data to any HTTPS endpoint you control. This page is about document delivery; it has nothing to do with billing or Stripe webhooks.

Setup

1. Open your parser's destination settings and choose Webhook.
2. Enter your endpoint URL. It must be a public HTTPS URL.
3. Optionally add custom headers, for example a secret header your endpoint checks to verify the request came from Parsedit.
4. Use Test send to fire a sample request and confirm your endpoint receives it.

What gets sent

When a document is delivered, Parsedit sends:

• Method: POST
• Content-Type: application/json
• Body: a JSON object with the document's extracted fields as key-value pairs, values formatted as readable strings.
• Headers: any custom headers you configured.

Requests time out after 10 seconds. A non-2xx response marks the delivery as failed, and the delivery status is visible on the document.

When it fires

• On Approve & Send in manual mode.
• Automatically on extraction completion or approval, if you enabled an auto-send mode. See Automation.

Verifying requests

Add a header like X-Webhook-Secret with a value only you know, and reject requests without it on your server. Since custom headers are stored with the destination and sent on every delivery, this gives you a simple shared-secret check.

Programmatic webhook subscriptions

The REST API offers a separate way to subscribe to document events with HMAC-signed payloads (X-Parsedit-Signature). See the API overview.

Receiving documents via webhook

To push documents into Parsedit instead, use the inbound webhook described in Document intake.