Skip to main content
The HTTP trigger accepts documents submitted programmatically via an HTTP POST request. Requests must include a valid API key for authentication. This trigger is ideal for integrating DocPipe into automated workflows and external systems.

​
Configuration

FieldTypeRequiredDescription
API keyselectYesThe API key used to authenticate incoming requests
Allowed originsstring[]NoList of allowed CORS origins for browser-based uploads
Accepted formatsstring[]NoRestrict which file formats are accepted (e.g., PDF, PNG)
Max size (MB)numberNoMaximum file size limit in megabytes

​
Inputs and outputs

Allowed inputs: None. This is a trigger node and starts the pipeline. Output: The uploaded file, passed to the next connected node.

​
Credit cost

0 credits. No cost to receive documents via the API.

HTTP trigger guide

Usage examples and integration patterns

API reference

Full API documentation

API keys

Manage your API keys

Upload trigger

Accept documents via the UI instead