Each API key is bound to one environment. Sandbox and live transaction codes are independent namespaces, so you can replay the same codes in both.
| Environment | Key prefix | Behavior |
|---|---|---|
| Sandbox | itms_test_ | Calculates against real rate data. Committed sandbox transactions are stored in an isolated namespace and never feed filings, nexus monitoring, collections, or production reporting. |
| Live | itms_live_ | Committed transactions enter your live compliance workflows. |
Live access enablement
Live access is enabled per workspace. A Prophit platform operator enables live access for your organization; once enabled, your organization admins can create, rotate, and revoke live keys directly in the Developer Console — no per-key support ticket. Until live access is enabled, live-key creation is declined and admins work entirely in sandbox.
Contact Prophit to enable live access for your workspace.
Sandbox isolation
Sandbox is a true testing environment: you can exercise the full integration end-to-end — including committed transactions, voids, and refunds — without any compliance side effects. Sandbox records are excluded from filing, nexus, collections, and analytics by environment.
Resolution and authority metadata
Every calculation response describes the authority and customer-visible quality of the result. These fields let an integration make safe decisions without exposing ITMS's internal content-processing methods:
calculation_authority/experimental— deterministic results are eligible for their documented workflows; experimental results are sandbox-only, non-authoritative, and cannot be committed or used for returns.jurisdiction_precision/jurisdiction_source— the precision and customer-visible resolution category used for the jurisdiction decision.rate_basis/rate_source_detail— stable customer-visible categories describing the rate content applied to the result.fallback_used/fallback_reason— whether an alternate supported calculation path served the request and why.address_validation_status/cass_grade_available— the address outcome and whether CASS-grade validation supported it.
See Schemas for the full metadata reference.