Skip to main content
This guide walks you through a complete Atlas verification workflow from first request to final results. By the end, you will have authenticated, created a flow, submitted documents for processing, and retrieved structured OCR data.

Sandbox Base URL

All API endpoints in this guide are relative to this base URL.
1

Get your credentials

Contact the Atlas account team to receive your Client-Id and Client-Secret. Store these securely—you will exchange them for a JWT token in the next step.You will also receive your provisioned product_type (for example, IDP_DEMO)
2

Generate an access token

Exchange your credentials for a JWT access token. The token expires after 3600 seconds (one hour).POST /v1/docstream/authtoken
Save the access_token. You will pass it as the Token header in every subsequent request.
3

Upload documents

Submit one or more document URLs for processing. Each document needs a file_url (a pre-signed URL pointing to the file in storage) and a document_id (your own reference for tracking).POST /v1/docstream/multiupload
Atlas begins processing immediately after upload. To get the data you can poll the extract endpoint in the next step.
4

Retrieve results

Poll this endpoint to monitor the state of your flow. You can use this alongside or instead of the callback.GET /v1/docstream/extracts?batch_id={batch_id}&page=1&per_page=50

What to build next

Now that you have end-to-end results, you can:
  • Set up your callback_url to receive results asynchronously and eliminate polling.
  • Set up your crosschecks to compare results and eliminate the need for human verification.
  • Map error_code values like INVALID_DOC and UNRECOGNISED into your exception handling workflow.
  • Apply similarity_score thresholds on cross_checks to automate accept/reject decisions.
  • Explore the full list of supported document types and their extracted fields in the Supported Documents reference.