Skip to main content
Atlas IDP Extraction APIs allow you to submit documents for OCR processing and receive structured JSON outputs containing extracted fields, confidence scores, document classifications, and validation metadata.
Base URLhttps://docstream.dev.kreditmind.comAll endpoints in this guide are relative to this base URL.
1

Generate an access token

Authenticate using your assigned credentials.

Endpoint

POST /v1/docstream/authtoken
curl --request POST \
  --url https://docstream.dev.kreditmind.com/v1/docstream/authtoken \
  --header "Client-Id: your-client-id" \
  --header "Client-Secret: your-client-secret"
The returned access_token must be passed as the Token header in all subsequent requests.
2

Upload documents for extraction

Submit one or more document URLs for processing.

Endpoint

POST /v1/docstream/multiupload

Request fields

FieldTypeRequiredDescription
product_typestringYesProduct type assigned by Atlas
file_urlsarrayYesList of documents to process
file_urls[].file_urlstringYesPre-signed URL of the document
file_urls[].document_idstringYesYour internal document reference
curl --request POST \
  --url https://docstream.dev.kreditmind.com/v1/docstream/multiupload \
  --header "Token: your-access-token" \
  --header "Content-Type: application/json" \
  --data '{
    "product_type": "LOAN_APP",
    "file_urls": [
      {
        "file_url": "https://your-bucket.s3.ap-south-1.amazonaws.com/pan.jpg",
        "document_id": "001"
      },
      {
        "file_url": "https://your-bucket.s3.ap-south-1.amazonaws.com/aadhaar.jpg",
        "document_id": "002"
      }
    ]
  }'
Atlas immediately starts processing the uploaded documents.
3

Poll extraction results

Retrieve extracted OCR data using the returned batch_id.

Endpoint

GET /v1/docstream/extracts

Query Parameters

ParameterRequiredDescription
batch_idYesBatch identifier returned from upload
pageNoPage number (default: 1)
per_pageNoNumber of results per page
curl --request GET \
  --url "https://docstream.dev.kreditmind.com/v1/docstream/extracts?batch_id=BATCH-30732-SIYKJ-20251121113228&page=1&per_page=50" \
  --header "Token: your-access-token"

Callback Support

Atlas supports asynchronous result delivery through callbacks. Share the following details with the Atlas team during onboarding:
  • callback_url — Endpoint where extracted results should be delivered
  • auth_url — Endpoint Atlas can call to obtain authentication credentials before posting results
Atlas maintains the callback configuration on our end, so these URLs only need to be shared once during setup. Once processing is complete, Atlas will automatically POST the extraction results to your configured callback endpoint.
Callback delivery is recommended for production environments as it eliminates the need for continuous polling and provides results as soon as processing is completed.

Example callback payload

{
  "data": [
    {
      "document_id": "001",
      "file_data": {
        "document_type": "AADHAAR",
        "name": {
          "value": "Yarlagadda Vijaya Lakshmi",
          "confidence_score": 1
        },
        "date_of_birth": {
          "value": "16/04/1983",
          "confidence_score": 1
        },
        "address": {
          "value": "W/O: Yarlagadda Siva Rama Krishna...",
          "confidence_score": 1
        }
      }
    }
  ],
  "page": 1,
  "per_page": 50,
  "total_pages": 1,
  "total_items": 5,
  "has_next": false,
  "has_prev": false
}
Refer to the Supported Documents section for the complete field-level extraction reference for every document type.