HTTP status codes returned by the CipherOwl API and what each means for your client — 200 success, 400 fix the request, 401 re-authenticate, 403 forbidden, 429 back off, 5xx retry.
The CipherOwl API uses standard HTTP response codes to indicate the success or failure of requests.
Success Codes
| HTTP Status Code | Description |
|---|---|
| 200 | Request successfully processed. |
Error Codes
| HTTP Status Code | Description |
|---|---|
400 | Bad request. Refer to the response body for details. |
401 | Bearer token expired. See Authentication for details. |
403 | User is not authorized to access the API. Note: An incorrect API path results in this error too. |
404 | Resource not found, or it belongs to another organization. Resources are scoped to your organization; one you cannot see is reported as missing, not forbidden. |
409 | Conflict. The resource already exists, or it changed since the version you supplied. |
429 | Request rate limit exceeded. |
500 | Unexpected server error. Contact CipherOwl support for assistance. |
Error responses from a service carry a JSON body with a message explaining the failure. A request rejected before it reaches a service — an expired token, a missing scope, an unknown path — is answered by the API gateway with a short plain-text body instead.