Sandbox-first API

Sandbox

Fixture-only testing for verification flows. No real identity data, documents, OTPs, or production API keys.

Fixture data onlyNo real PIIIdempotencyConsent purposeProduction review

Quickstart Use fixture sandbox View changelog

3-call sandbox pattern

curl -X POST https://sandbox.pramaan.online/v1/verify \
  -H "Authorization: Bearer $PRAMAAN_SANDBOX_KEY" \
  -H "Idempotency-Key: demo-fixture-001" \
  -H "Content-Type: application/json" \
  -d '{
    "subject": {
      "name": "Sandbox Worker",
      "phone": "+910000000000"
    },
    "purpose": "household_help_verification_demo",
    "checks": ["identity", "address"],
    "fixture": "fixture_green_domestic_help"
  }'

Fixtures

Test states without touching real people.

Current

Green fixture

Successful consented identity/address sample using dummy data only. Code: fixture_green_domestic_help

Current

Amber fixture

Manual-review sample for mismatch handling and support escalation. Code: fixture_amber_name_mismatch

Current

Red fixture

Failure-state sample for error handling. Not a real person or production record. Code: fixture_red_expired_document

Keep sandbox keys and production API keys separate.

Sandbox keys are for fixture payloads only. Production keys are issued only after purpose, consent, logging, DSR, and support routes are reviewed.

Never paste real API keys, Aadhaar, PAN, OTPs, raw documents, or private keys into examples, screenshots, tickets, or chat.

Build consent-first verification carefully.

Start in sandbox with fixture data, then move to production only after purpose, consent copy, logging, DSR, and support routes are reviewed.

Open sandbox Read API docs