# DigiParser Webhooks | Receive Signed Document Result Events

Source: https://www.digiparser.com/integrations/webhooks

[<- All integrations](/integrations)

Webhook export

# When the document is ready,  
your system gets the event.

Receive extracted fields, tables, and document metadata at your endpoint. Verify the signed request, accept it quickly, and let your backend handle the next step.

[Start free ↗](https://app.digiparser.com/auth/join)[Setup documentation ->](/docs/guides/integrations/using-webhooks)

## Receive processing events in your own application.

Build a receiver that verifies incoming events before it acts on them. Store accepted events and respond promptly before starting downstream work.

1.  1Verify the webhook signature.
2.  2Store the event and return a successful response.
3.  3Run the downstream work from the accepted event.

![](/_next/image?url=%2Fimages%2Fintegrations%2Fwebhooks-workflow-v1.webp&w=3840&q=75&dpl=dpl_4CEHPWQCJofunboV6oYnMCcudHh5)

{
  "event": "document.exported",
  "data": {
    "id": "doc\_example",
    "extracted\_data": {
      "Invoice Number": "INV-1042",
      "Total": 240
    },
    "metadata": {
      "name": "invoice-1042.pdf",
      "isApproved": true
    }
  }
}

Illustrative payload - abbreviated

### Your parser defines the data.

The keys inside extracted\_data match the fields and tables you configured. Table values arrive as rows, and metadata provides document context.

Use the full [webhook reference](/docs/api/webhooks) for the payload contract.

## Separate delivery from downstream work

Recommended receiver sequence

1.  01Read raw body and Svix headers
2.  02Verify the endpoint signature
3.  03Store the accepted event
4.  04Return 2xx
5.  05Process your business action

Acknowledge the accepted payload quickly. Run slow ERP requests or reporting jobs after receipt. Design the downstream write to handle repeated delivery without duplicate business records.

## Configure a receiver

1.  01
    
    ### Add Export via webhook
    
    Open the parser's Integrations page and add the webhook export.
    
2.  02
    
    ### Add your HTTPS endpoint
    
    Use a publicly reachable receiver. You can configure multiple endpoints for different systems.
    
3.  03
    
    ### Configure signature verification
    
    Each endpoint has its own signing secret. Verify the raw request body with svix-id, svix-timestamp, and svix-signature using the documented verification method.
    
4.  04
    
    ### Process a representative document
    
    Complete any required approval, then inspect the received event and confirm field and table mappings in your receiver.
    
5.  05
    
    ### Check network and response behavior
    
    If a firewall is used, follow the complete current IP list in the verification guide. Respond with a successful 2xx status after accepting the event.
    

## Delivery follows the document's review workflow

### No review required

The result is sent after processing. Your receiver can use extracted data for a reporting table, ERP intake queue, or another internal service.

### Review required

The export waits for the applicable approval. Keep the downstream operation tied to the delivered event rather than guessing that upload means completion.

## Use the event where it belongs

Example receiver responsibilities

Business process

Your receiver handles

Supplier invoice -> AP system

Vendor lookup and bill creation according to your rules

Customer PO -> sales system

Customer matching and order creation

Statement -> warehouse

Transaction storage and reporting ingestion

Webhook delivery carries the result. Your code controls the destination operations and business rules. For JavaScript that runs inside DigiParser, see [Custom Code Export](/integrations/custom-code-export).

[Start free ↗](https://app.digiparser.com/auth/join)[Setup documentation ->](/docs/guides/integrations/verifying-webhooks)