Sandbox vs Production

Two environments, identical schemas. Sandbox at apisandbox.whitebooks.in is free, throttled at 60 req/min/key, and uses sample GSTINs. Production at api.whitebooks.in is plan-gated and uses your real GSTIN — but the request/response shape is identical, so a working sandbox integration is a working production integration.

Side-by-side

PropertySandboxProduction
Base URLapisandbox.whitebooks.in/{product}api.whitebooks.in/{product}
GSTINSample GSTIN providedYour real GSTIN
Rate limit60 req/min/keyPlan-based (Starter 100 req/s → Enterprise burstable)
Real filingsNo (writes go to a stub)Yes (writes go to GSTN / IRP / NIC)
IRP behaviourDeterministic — returns mock IRN + signed QRLive IRP; subject to upstream availability
OAuth tokenSeparate sandbox client_id + client_secretProduction client_id + client_secret
CostFreePlan price (Talk to sales → Talk to sales)
SLABest-effort99.5% → 99.99% by tier

Migration steps

  1. Build + verify on sandbox until your integration passes your own tests
  2. Request production credentials at /about/contact-us
  3. Swap env: 'sandbox' → 'production' in your SDK config (or change the base URL on raw REST clients)
  4. Swap the OAuth client_id + client_secret pair
  5. Run a single low-stakes call (GSTIN verify) to validate connectivity before going live

Schema parity guarantee

We do not run drift between sandbox and production. Any change to the request/response shape ships to both environments simultaneously (or to sandbox first, with at least 30 days of advance notice in /changelog before production rollout).

/openapi/index.json →Discovery — all 3 specs Authentication →OAuth 2.0 details Rate limits →Per-tier throughput numbers Status →Live uptime + incidents

Part of the WhiteBooks developer documentation cluster. See /llms.txt for the full machine-readable site index. Last updated 27 May 2026.

Schedule Demo