Execute a custom processor configuration. The pipeline_id must reference a completed custom processor ID or a template ID.
The custom pipeline ID or template ID to execute. Must be a completed pipeline created via the custom pipeline API, or a valid template slug.
Optional file URL (http/https). If provided, the server will download and process it.
Optional version number to use. If not provided, the active version of the pipeline will be used.
Run evaluation rules defined for this custom pipeline.
Output mode for the underlying parsing step.
The maximum number of pages to process.
The page range to process, comma separated like 0,5-10,20.
The output format. Can be 'json', 'html', 'markdown', or 'chunks'. Defaults to 'markdown'.
Whether to paginate the output. If set to True, each page of the output will be separated by a horizontal rule that contains the page number.
Add data-block-id attributes to HTML elements for citation tracking. Only applies when output_format includes 'html'.
Include markdown field in chunks and JSON output. When enabled, each chunk will have a 'markdown' field with the markdown representation of that block. Only applies when output_format includes 'json' or 'chunks'.
Disable image extraction from the PDF. Defaults to False.
Disable synthetic image captions/descriptions in output. Images will be rendered as plain img tags without alt text. Defaults to False.
Skip the cache and re-run.
Optional webhook URL to call when the request is complete.
Optional workflow step data ID to associate with this request.
Input PDF, word document, powerpoint, or image file, uploaded as multipart form data. Images must be png, jpg, or webp format.
Successful Response
The ID of the request. This ID can be used to check the status of the request.
The URL to check the status of the request and get results.
Whether the request was successful.
If the request was not successful, this will contain an error message.
A dictionary of the versions of the libraries used in the request.