On this page
Errors and Troubleshooting
| Status | Meaning | Next action |
|---|---|---|
400 | Invalid JSON, envelope, method, schema, or required field. | Compare the request with the active operation schema. |
401 | Client, bearer credential, audience, expiry, or revocation failed. | Confirm the binding and rotate if necessary. |
403 | Required scope or approval grant is absent. | Request the minimum appropriate grant. |
404 | Gateway, operation, or active publication is unavailable to this binding. | Confirm environment and publication state. |
405 | HTTP or logical operation method differs. | Use POST at the gateway and the contracted logical method. |
429 | Operation rate policy exceeded. | Back off with jitter. |
5xx | Runtime, schema installation, contract integrity, or certified handler failed. | Retain the request ID and contact support. |
Error responses include a stable error.code, safe error.message, UTC timestamp, and request_id. They do not return stack traces, credentials, private contract definitions, or unrestricted payloads.
Diagnostic checklist
- Use
https://batoi.com/api/unless compatibility requires the configured host. - Preserve the
POSTmethod, body, and authorization header. - Confirm client ID, gateway UID, environment, operation, and scope belong to the same binding.
- Compare the returned contract hash with the published reference.
- Provide only the correlation identifier to support; never attach credentials or unrestricted payloads.