Support

Before opening a ticket

Check support-and-status — if there's an active incident, support already knows and is working on it.
Look up the error response's code at https://docs.isaapi.com/docs/errors-<code> — each error code has a remediation page covering common causes.
Search docs.isaapi.com — the quickstart, authentication, and error guides answer most integration questions.

Technical support

Use this channel for:

Unexpected API behavior
SDK bugs or feature requests
Integration questions not answered by the documentation
Requests for request_id correlation (attach the request_id from the error response)

Include in every ticket:

Field	Where to find it
`request_id`	Error response body (`request_id`) or `X-ISA-Request-Id` response header
`idempotency_key`	The `Idempotency-Key` header you sent, or the `idempotency_key` echo in the response envelope
HTTP status and `code`	Error response body
Timestamp (UTC)	When the request was made
Account name or token prefix	The `isa_live_` or `isa_test_` prefix (never send the full token)

Including a request_id lets support find your request in server logs instantly. Without it, support must search by account and timestamp, which is much slower.

Response time: one business day for standard tier; four business hours for professional tier.

Account and billing

Email: [email protected]

Use this channel for:

Provisioning a new account or adding seats
Quota increases or plan upgrades
Custom procurement or net-30 invoicing
Token rotation when dashboard access is unavailable

Dashboard

dashboard.isaapi.com — self-serve for:

Generating and rotating API keys
Viewing usage and quota consumption
Managing webhook subscriptions
Downloading invoices

Status and incidents

support-and-status — incident communications and real-time API availability. Subscribe for email or webhook notifications on incidents and maintenance.