Test mode

Every request runs in one of two modes: test or live.

The mode is determined by your token prefix — there is no toggle in the request, no ?test=true query string, and no separate hostname. Use test mode for integration work, CI, and manual exploration. Use live mode when you're in production.

Token prefix	Mode	What it touches
`isa_live_`	Live	Real underwriting, real quota, real audit log
`isa_test_`	Test	Sandbox underwriting, no quota consumption, isolated audit log

The host is the same for both modes: https://zyins.isaapi.com. Every response envelope includes a livemode field (true or false) showing which mode processed the call.

What test mode simulates

Prequalify and quote return real engine output — the same underwriting decision a live token would receive for identical input.
Persistence writes to a test-mode database reset weekly. Anything you create (cases, documents, signing sessions) survives until Sunday at 00:00 UTC.
Webhooks fire against any URL you register. Test-mode events carry livemode: false in the payload and ISA-Mode: test in the headers.
Rate limits are enforced at one-tenth live quota, so you can trigger 429 rate_limit_exceeded errors in CI.

What test mode does not simulate

Document signing. Test-mode signatures are accepted but never sent to the signing provider. The signed PDF is a placeholder.
Email delivery. Test-mode email goes to a capture sink, not the recipient. View captured emails in the dashboard.
Payment. Billing endpoints reject test-mode tokens. Exercise payment flows only with live tokens.

Getting a test token

Issue both keys yourself in the dashboard at app.isaapi.com/settings/api-keys: sign up, accept the API agreement, and create an isa_test_ key (free, sandbox) alongside your isa_live_ key. There is no separate request for a test token.

Important: Tokens are shown only once, at creation. Store them in a secrets manager immediately.

The dashboard also rotates keys — with an optional 1h, 24h, or 72h grace period — and revokes them; revocation takes effect within 60 seconds. For custom procurement with one-business-day turnaround, email [email protected].

Lost your token?

Tokens are shown once at creation and not retained by the platform. If you lose a test token before storing it, rotate the key from the dashboard — the old key can keep working for an optional grace period of 1 hour, 24 hours, or 72 hours so in-flight requests don't fail, and revocation takes effect within 60 seconds. Live-mode keys are not affected — each mode has independent credentials.

Switching from test to live

Replace ISA_TOKEN=isa_test_... with ISA_TOKEN=isa_live_... in your deployment environment.
Re-register your webhook subscriptions in live mode — test-mode subscriptions do not carry over.

No code change is needed. The SDK reads the env var, the token prefix determines the mode, and both modes use the same endpoint.

Identifying mode in logs and dashboards

Every response envelope carries livemode: true | false, as does every webhook payload and dashboard view.

Always store livemode alongside request_id and idempotency_key on every business record. This triple uniquely identifies the API call that produced the record and protects against mode confusion when code moves from dev to staging to production.

Service status

Until the public status page launches at GA, availability incidents are emailed to all active integrators. See support-and-status for details.

Subscribe to incident notifications to receive email or webhook alerts when degradation occurs. The status page will track test-mode and live-mode availability independently.