The webhook trigger lets you submit documents to a pipe via API, enabling programmatic integration with your applications.Documentation Index
Fetch the complete documentation index at: https://docs.docpipe.ai/llms.txt
Use this file to discover all available pages before exploring further.
Prerequisites
- A pipe with a Webhook trigger node in its pipeline
- An API key with trigger permissions
Endpoint
Authentication
Include your API key in theX-Api-Key header:
Request
Send the document asmultipart/form-data with the file in the file field.
cURL
JavaScript
C#
Python
Response
A successful request returns the trigger result with details about the created run.Idempotency
To prevent duplicate document submissions (for example, due to network retries), include anIdempotency-Key header with a unique GUID:
409 Conflict instead of creating a duplicate. The key is optional: if omitted, the request is processed normally without deduplication.
Only successful (2xx) responses consume the key. If a request returns 4xx or 5xx, you can safely retry the same Idempotency-Key; the next successful retry is the one that locks the key in.
Error handling
Common errors:| Status | Cause |
|---|---|
401 | Missing or invalid API key |
400 | Unsupported document format or document exceeds size limit |
404 | Pipe not found or not active |
409 | Duplicate request: the Idempotency-Key has already been processed |
Webhook trigger configuration
The webhook trigger node in your pipeline can be configured with:- Allowed origins: restrict which origins can submit documents (CORS)
- Accepted formats: limit accepted document formats
- Max size (MB): set a maximum document size