Segment Document
Segment a document into sections using a schema. Returns page ranges for each identified segment. Provide a file for end-to-end processing, or a checkpoint_id from a previous /convert call.
Authorizations
Body
JSON object (passed as a string) defining how to segment the document: {"segments": [{"name": ..., "description": ...}, ...], "segmentation_strategy": "custom"}. When 'segments' are provided they guide which sections to identify; for fully automatic document-boundary detection pass {"segmentation_strategy": "document_boundary"} with no segments. The same object (JSON-encoded) is used for segment steps in pipelines via settings.segmentation_schema.
Optional file URL. Provide either file/file_url or checkpoint_id.
Checkpoint ID from a previous /convert request (with save_checkpoint=true). Skips re-parsing when provided.
Output mode for parsing (only used when providing a file, not a checkpoint).
The maximum number of pages to process.
The page range to process, comma separated like 0,5-10,20.
Save a checkpoint after processing for future extraction/segmentation calls.
Skip the cache and re-run.
Optional webhook URL to call when the request is complete.
Optional residency region override (e.g. us, eu). When provided, use file_url or direct-upload; multipart uploads are rejected. When omitted, the request uses the team's configured residency and profile.
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.
Response
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.