API Sandbox
LiveRequests hit the live API. Rate limits and billing apply. Key prefix: tc_live_
Request
Enter your API key above to send requests.
Response
Hit Send to see the API response here.
No response yet
Requests go from your browser to https://api.t-code.tn/api/v1/external using your key as the Bearer token. Live rate limits: 30 req/min and 5 000 req/day. Remaining quota is shown next to your key after each request.
Why sandbox keys can’t be used in production
Distinct key prefix
Sandbox keys start with tc_test_. Live keys start with tc_live_. Instantly visible in any code review or audit.
Backend enforcement
The API server rejects tc_test_ keys on billing-sensitive paths and flags them in audit logs if called from non-localhost origins.
Response watermark
Every sandbox response includes "_env":"sandbox". Any production monitoring pipeline will immediately surface misuse.
Fixture data only
Sandbox returns consistent test fixtures, not real Tunisian address records. A live app relying on it ships wrong data to users.
No SLA
Sandbox has no uptime guarantee and can go offline for maintenance without notice — a live app depending on it will break naturally.
No billing impact
Sandbox requests don't count toward quotas or invoices. If you see zero usage in billing, your app is likely using a sandbox key.