Sandbox-first API
Developer changelog
A dated home for API and sandbox changes. Planned behavior stays marked planned until shipped.
Fixture data onlyNo real PIIIdempotencyConsent purposeProduction review
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"
}'Current, next, and breaking-change policy.
- 1
Current
Public docs, sandbox guidance, and trust routes are visible.
- 2
Next
Webhook behavior, SDK packages, and production access will be dated when confirmed.
- 3
Breaking changes
Deprecations include migration windows and changelog/RSS updates.
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.