job_id immediately, and retrieve the result when the job completes.
Use Extract Jobs for long-running extractions, such as extracting from long documents or with large, complex schemas.
Endpoints
The request fields are the same as the synchronous Extract API. See Extract Input Parameters. Extract Jobs uses these endpoints:Workflow
- Build your extraction schema. See Extraction Schema (JSON).
- Submit the Markdown and schema to
POST /v2/extract/jobs. - Get the
job_idfrom the response. - Poll
GET /v2/extract/jobs/{job_id}untilstatusiscompleted. - Read the extracted fields from the job’s
result, or fromoutput_urlif you saved the output to a URL. See Extract API Response.
Create a Job
Send the same fields you would send to the synchronous endpoint. ReplaceYOUR_API_KEY with your API key and parse-output.md with the path to your Markdown file.
202 response with the job_id and the initial status:
Choose a Service Tier
Set the optionalservice_tier form field to control the job’s turnaround time and credit consumption.
If you omit service_tier, the job runs on the standard tier.
For how the tiers compare, see Sync vs Async Processing. For credit consumption by tier, see Credit Consumption.
Set the tier.
Include the
service_tier field in your create-job request:
Get a Job
Poll the job with itsjob_id:
Job Statuses
Save Extraction Output to a URL
To write the extraction result to your own storage instead of retrieving it inline, pass the optionaloutput_save_url parameter when you create the job. The result (the same shape as a synchronous response, including metadata with billing) is delivered to that URL, and the poll response reports output_url instead of result. The completed poll response also carries the job’s metadata, so billing information is available without fetching the file.
The output_save_url parameter is accepted only on job creation; the synchronous /v2/extract endpoint rejects it with a 422 error. The URL must be a presigned URL that grants time-limited write access to a single object, with the same requirements as Parse Jobs; see URL Requirements.