Run Processor
Run processors (extraction, classification, splitting, etc.) on a given document.
Similar to workflow runs, processor runs are asynchronous and will return a status of PROCESSING
until the run is complete.
- You can configure webhooks to receive notifications when a processor run is complete or failed.
- Or you can poll the get endpoint for updates on the status of the processor run.
Headers
Bearer authentication of the form Bearer <token>, where token is your auth token.
API version to use for the request. If you do not specify a version, you will either receive a 400 Bad Request
or be set to a previous legacy version. See API Versioning for more details.
Request
The ID of the processor to be run.
Example: "dp_Xj8mK2pL9nR4vT7qY5wZ"
An optional version of the processor to use. When not supplied, the most recent published version of the processor will be used. Special values include:
"latest"
for the most recent published version. If there are no published versions, the draft version will be used."draft"
for the draft version.- Specific version numbers corresponding to versions your team has published, e.g.
"1.0"
,"2.2"
, etc.
The file to be processed. One of file
or rawText
must be provided. Supported file types can be found here.
A raw string to be processed. Can be used in place of file when passing raw text data streams. One of file
or rawText
must be provided.