Environments

USBC ships APIs in two developer-facing environments. Pick Sandbox for development and testing; promote to Production when you're ready for real users.

Quick reference

Environment	Base URL	Auth audience	Use for
Sandbox	`https://api.kong.globalid.dev`	`uns-sandbox`	Development, integration testing, demos
Production	`https://api.kong.global.id` (coming soon)	`uns-prod`	Real users, real money

What's different

Aspect	Sandbox	Production
Data	Fake test users and transactions	Real users, real records
KYC providers	Test mode (auto-approve)	Live verification with full SLA
Webhooks	Delivered to any HTTPS URL	Delivered to allow-listed URLs only
Rate limits	Relaxed — 100 req/min per app	60 req/min per app (default tier)
Cost	Free	Per the billing tier on your account
Token audience	`uns-sandbox`	`uns-prod`
App approval	Auto-approved on registration	Requires manual review by the platform team

Moving from Sandbox to Production

Open a Production application registration. The portal walks you through legal/compliance disclosures.
Wait for approval (usually within one business day).
Receive Production client_id + client_secret — distinct from your Sandbox credentials.
Swap the base URL and credentials in your service config. Never share Sandbox credentials with Production code or vice versa.
Run a small canary against Production before flipping the full rollout.

Production tokens won't work against Sandbox endpoints, and Sandbox tokens won't work against Production endpoints — audience checks at the gateway reject mismatches with a 401.

Versioning across environments

APIs are versioned independently per environment:

Sandbox tracks the next release — expect breaking changes earlier than Production.
Production tracks the stable release — breaking changes are announced 30 days in advance via the release notes (coming soon).

If you need to pin to a specific version against Sandbox, use the X-USBC-Api-Version: 2026-04-01 header.