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.

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

Tokens are issued automatically after checkout at checkout.isaapi.com.

Within a few minutes, you'll receive an email from [email protected] containing both your test and live tokens, a curl sample, and a quickstart link. There is no separate request for a test token — both arrive together.

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

Self-service token rotation is coming soon. Until then, use the credentials email. For custom procurement with one-business-day turnaround, email [email protected].

Lost your token?

Tokens are shown once at provisioning and not retained by the platform. If you lose a test token before storing it, email [email protected] with your account name and "lost test token" in the subject line.

Support will rotate the key immediately. The old key gets a 24-hour grace period so in-flight requests don't fail. Live-mode keys are not affected — each mode has independent credentials.

Switching from test to live

1. Replace ISA_TOKEN=isa_test_... with ISA_TOKEN=isa_live_... in your deployment environment.
2. 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.