Authentication
Every request to /v1 (except status and the OpenAPI spec) needs an API key.
Sending your key
Send it as a bearer token. The x-api-key header is also accepted for older clients.
bash
curl "https://tax-api-dev.itensiahr.com/v1/jurisdictions" \
-H "Authorization: Bearer $ITX_API_KEY"Live and test keys
| Prefix | Use for | Billing |
|---|---|---|
itx_live_ | Production traffic | Successful requests count toward your monthly quota |
itx_test_ | CI, staging and local development | Never billed and not counted toward the quota; rate limits still apply |
Both return the same published data.
Managing keys
Create, name and revoke keys in your dashboard. You can have up to 10 active keys. We store only a SHA-256 hash, so a key is shown once when it is created — if you lose it, revoke it and create another.
Rotate without downtime: create a new key, deploy it, confirm traffic in the dashboard's usage tab, then revoke the old one. Revocation takes effect within 30 seconds.
Request ids
Every response carries an x-request-id header (also in meta.request_id, and in error.request_id on errors). Log it alongside your own trace id and include it when you contact support.