Skip to main content
The /extract_async endpoint is deprecated and will be removed in a future version. Please migrate to /extract with async: true as described below.

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 — use GET /job/{job_id} to check status and retrieve results. No changes are needed to your polling logic.

FAQ

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.
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.
No. Webhook notifications work the same way regardless of which endpoint initiated the job. The job.completed event payload is unchanged.
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.

Extract Endpoint

Full reference for the unified /extract endpoint

Async Processing

Guide to async processing and job polling