Overview
The/extract_async endpoint has been replaced by a single, unified /extract endpoint that supports both synchronous and asynchronous processing via an async flag. This simplifies the API surface — you no longer need to choose between two different endpoints.
Migration Steps
Code Examples
Python SDK
TypeScript SDK
curl
Polling for Results
Polling works exactly the same way — useGET /job/{job_id} to check status and retrieve results. No changes are needed to your polling logic.
FAQ
Will /extract_async stop working immediately?
Will /extract_async stop working immediately?
No. The endpoint will continue to work for backward compatibility but will be removed in a future version. We recommend migrating as soon as possible.
Are there any behavioral differences?
Are there any behavioral differences?
The unified
/extract with async: true behaves identically to /extract_async. The only addition is a message field in the async response. Your existing polling and webhook integrations will continue to work unchanged.Do I need to update my webhooks?
Do I need to update my webhooks?
No. Webhook notifications work the same way regardless of which endpoint initiated the job. The
job.completed event payload is unchanged.Can I still use sync extraction?
Can I still use sync extraction?
Yes! With the unified
/extract endpoint, you get both modes in one place. Omit the async flag (or set async: false) for synchronous extraction, or set async: true for asynchronous processing.Related
Extract Endpoint
Full reference for the unified /extract endpoint
Async Processing
Guide to async processing and job polling