Extract File Async (Deprecated)
Deprecated: Use /extract with async: true instead.
Starts an asynchronous extraction job. The request mirrors the synchronous options but returns immediately with a job identifier that clients can poll for completion status.
Overview
The asynchronous extraction endpoint accepts the same input parameters as the synchronous/extract endpoint but returns immediately with a job identifier. Use this endpoint for:
- Large documents that may take longer to process
- Batch processing workflows
- Non-blocking integrations
Migration
Replace calls to/extract_async with /extract and add async: true:
Request
Document Source
Provide the document using one of these methods:Extraction Options
Figure Processing
Settings underfigure_processing control how figures (images, charts, diagrams) and embedded visuals are processed. Applies to both PDFs/images (figures detected from layout) and spreadsheets (charts and embedded images read directly from the workbook). Affects the markdown output and the bounding_boxes.Images[] array.
show_images: true collects every embedded chart and image in the workbook and emits one entry per visual under bounding_boxes.Images, with chart-specific fields like chart_type, chart_title, and source_ranges populated. See Bounding Boxes for the full field list.Spreadsheet Options
Settings underspreadsheet control how Excel workbooks (.xlsx, .xlsm, .xls) are processed. By default, hidden rows, columns, and sheets are excluded from extraction output, cell values are rendered the way Excel displays them, and table cell metadata is included. Phantom-cell trimming is opt-in. Spreadsheet responses are returned as full-result URLs by default because workbook cell_data can make the payload large even for modest .xlsx files.
includeHiddenRows, onlyDataRows, cellData) and snake_case (include_hidden_rows, only_data_rows, cell_data) formats.Phantom-cell trimming (only_data_rows / only_data_cols)
Excel files exported from claims systems, ERPs, and other automated pipelines routinely declare a “used range” that extends hundreds of thousands of rows past where the data actually ends. A typical case: a 57 MB workbook with only ~500 rows of real data, where the other ~1,000,000 rows are empty cells that exist only because they were once selected and styled. These phantom cells inflate file size by orders of magnitude and can exhaust parser memory on the extraction pipeline.
Set only_data_rows: true and only_data_cols: true to have Pulse scan each sheet once before parsing, find the largest row and column containing a value or formula, and ignore everything beyond that extent. Surviving cells keep their original A1 coordinates (e.g., a value at B7 in the source is still B7 in the output), so any citation or bounding box that references a specific cell remains stable. The trim only kicks in on large sheets (≥5 MB of XML per sheet), so small, well-formed workbooks pay no overhead either way.
Both flags default to false.
Pulse Ultra 2 Options
These options are available only whenmodel: pulse-ultra-2 is set. Passing any of them with the default model returns a 400 error listing the offending fields.
Selection mark detection
Usedetect_selections: true with model: pulse-ultra-2 when a document contains forms, checkboxes, radio buttons, handwritten selection marks, or other marked-choice controls. Pulse runs a specialized detection pass for these marks so selected/unselected states are less likely to be missed or confused with nearby text, boxes, or handwriting. When available, the detected state is returned on the relevant bounding-box items as selected.
Markdown output additions
Whenextract_figure or figure_description is enabled, figures in response.markdown include additional tags:
refine (or refine_options) is set, markdown content is post-processed page-by-page; output is cleaner but typically grows ~1.5–3x in size for dense documents. No new tags are introduced.
Extensions
Settings underextensions enable additional processing passes or alternate output formats. Each enabled extension produces a corresponding output field under response.extensions.*. For example, enabling extensions.chunking produces response.extensions.chunking, and enabling extensions.alt_outputs.return_html produces response.extensions.alt_outputs.html.
Storage Options
Control whether extractions are saved to your extraction library:Deprecated Fields
The following input fields are deprecated and will be removed in a future version. They are still accepted for backward compatibility.warnings array directing you to the updated field names. See the latest documentation for details.Response
When you submit a document for async extraction, you’ll receive a response containing the job metadata:Response Fields
Retrieving Results
After submitting an async extraction, poll the job status endpoint to retrieve results:Example Usage
Submit Async Extraction
With Structured Output
Cancel a Job
Authorizations
Body
Input schema for extraction requests. Provide either file (direct upload) or fileUrl (remote URL).
Document to upload directly. Required unless fileUrl is provided.
Public or pre-signed URL that Pulse will download and extract. Required unless file is provided.
Extraction model to use. When set to pulse-ultra-2, routes the request through Pulse Ultra 2 (self-hosted VPC model) instead of the default cloud-based service. If omitted or set to default, the default model is used.
default, pulse-ultra-2 Pulse Ultra 2 only. Enables a specialized selection-mark detection pass that improves selected/unselected state accuracy for forms, checkboxes, radio buttons, handwritten checkmarks, X marks, and similar controls. Enabled by default when model is pulse-ultra-2; set to false to skip this pass. Passing true without model: pulse-ultra-2 returns a validation error.
UUID of a saved extraction configuration (a "preset"). When provided, the server loads the saved configuration and applies its options on top of any inline parameters supplied in this request. Inline parameters always take precedence over preset values for the same field. Saved configs are managed via the platform UI or the input_extractions admin endpoints.
Page range filter supporting segments such as 1-2 or mixed ranges like 1-2,5.
^[0-9]+(-[0-9]+)?(,[0-9]+(-[0-9]+)?)*$When true, return the complete extraction result as a URL even if it is small. Spreadsheet extractions use URL delivery by default; set force_url: false to request inline spreadsheet output. URL delivery changes only the transport, not the result shape.
Settings that control how figures and embedded visuals are processed. Applies to both PDFs/images (where figures are detected from layout) and spreadsheets (where charts and embedded images are read directly from the workbook). These options affect the markdown output and the bounding_boxes.Images[] array; they do not produce additional output fields elsewhere in the response.
Settings that enable additional processing passes or alternate output formats. Each enabled extension produces a corresponding output field under response.extensions.*.
Settings for Excel/spreadsheet extraction. Controls handling of hidden rows, columns, and sheets, whether numeric cells are rendered using their display format or underlying raw value, whether table cell metadata is captured, and optional trimming of empty phantom rows/columns past the last data-bearing cell. Applies to .xlsx, .xlsm, and .xls files. Accepts both camelCase and snake_case field names.
Options for persisting extraction artifacts. When enabled (default), artifacts are saved to storage and a database record is created.
If true, returns immediately with a job_id for polling via GET /job/{jobId}. Otherwise processes synchronously.
⚠️ DEPRECATED — Use the /schema endpoint after extraction instead. Pass the extraction_id from the extract response to /schema with your schema_config. This parameter still works for backward compatibility but will be removed in a future version.
(Deprecated) JSON schema describing structured data to extract. Use structuredOutput instead. Accepts either a JSON object or a stringified JSON representation.
(Deprecated) Natural language prompt for schema-guided extraction. Use structuredOutput.schemaPrompt instead.
(Deprecated) Custom instructions that augment the default extraction behaviour. Use figureProcessing or extensions instead.
⚠️ DEPRECATED — Use extensions.chunking.chunkTypes instead. Comma-separated list of chunking strategies to apply (for example semantic,header,page,recursive). Still accepted for backward compatibility.
⚠️ DEPRECATED — Use extensions.chunking.chunkSize instead. Override for maximum characters per chunk when chunking is enabled.
x >= 1⚠️ DEPRECATED — Toggle to enable figure extraction in results.
⚠️ DEPRECATED — Use figureProcessing.description instead. Toggle to generate descriptive captions for extracted figures.
⚠️ DEPRECATED — Use figureProcessing.showImages instead. Embed base64-encoded images inline in figure tags in the output. Increases response size.
⚠️ DEPRECATED — Use extensions.altOutputs.returnHtml instead. Whether to include HTML representation alongside markdown in the response.
(Deprecated) Enables expanded rationale output for debugging.
Response
Asynchronous extraction job accepted
Acknowledgement returned when a request is submitted for asynchronous processing. Poll GET /job/{job_id} to check status and retrieve results.
Identifier assigned to the asynchronous job.
Initial status reported by the server.
pending, processing, completed, failed, canceled Human-readable description of the accepted job.
Deprecated — Timestamp indicating when the job was accepted. Retained for backward compatibility. Use GET /job/{jobId} for timing details.
Number of credits consumed by this request. Only present when the organization has the credit billing system enabled.