Endpoint
Request headers
string
required
JWT access token obtained from POST /authtoken.
Query parameters
string
required
The batch identifier returned from the upload API. Atlas returns extracted document data associated with this batch.Example:
BATCH-69469-BBRSS-20260309081408integer
Page number for pagination.Default:
1integer
Number of records returned per page.Default:
50Response
array
Array of extracted document results.
string
The document identifier provided during upload.
object
Structured OCR output for the document. Fields vary depending on the detected document type.
integer
Current page number.
integer
Number of records returned in the response.
integer
Total number of pages available.
integer
Total number of extracted documents available.
boolean
Indicates whether additional pages are available.
boolean
Indicates whether previous pages are available.
Example
Understanding the response
Thedata array contains one object for each processed document in the batch.
Each document includes:
Every extracted field contains:
confidence_score ranges from 0 to 1 and represents Atlas’s confidence in the extracted value.
Callback support
Instead of polling the extracts endpoint, Atlas can deliver extraction results directly to your system through a callback URL. When callback integration is enabled for your account:- Atlas processes the uploaded documents.
- Atlas sends the extraction results to your configured
callback_url. - Your endpoint receives the same extraction payload automatically when processing is complete.
- Your
callback_urlwhere results should be delivered - Your
auth_urlused by Atlas to authenticate before sending callbacks
Callbacks are recommended for production integrations because they eliminate the need to continuously poll the extracts endpoint and allow your systems to receive results as soon as processing completes.

