internal_error

HTTP status: 500

The server hit an unhandled error while processing your request. This is our problem, not yours — a well-formed request should never produce a 500. The failure is logged against the request_id in the response.

Why this happens

• An unhandled exception in a server-side code path.
• A dependency returned a response the server could not interpret.
• A deploy regression. These are tracked as incidents.

You did nothing wrong at the request layer. If you see a sustained stream of internal_error, it is an outage on our side.

What to do

1. Retry once with the same Idempotency-Key after a short backoff — many 500s are transient. The SDKs retry automatically.
2. If it persists, file a ticket at [email protected] and quote the request_id. That value correlates directly to the server-side log entry and is the fastest path to a root cause.
3. Check support-and-status for an active incident before filing.

Example response

{
  "type": "https://zyins.isaapi.com/errors/internal-error",
  "title": "Internal server error",
  "status": 500,
  "detail": "An unexpected error occurred. Quote request_id 'req_01HZK2N5GQR9T8X4B6FJW3Y1AS' when contacting support.",
  "code": "internal_error",
  "param": null,
  "request_id": "req_01HZK2N5GQR9T8X4B6FJW3Y1AS"
}

SDK exceptions

See also

• Error catalog
• service_unavailable — a downstream dependency is degraded
• timeout — a downstream call exceeded its deadline