Error Codes
Troubleshoot problems with this comprehensive breakdown of all error codes.
Response codes
Nomos uses standard HTTP codes to indicate the success or failure of your requests.
In general, 2xx HTTP codes correspond to success, 4xx codes are for user-related failures,
and 5xx codes are for infrastructure issues.
| Status | Description |
|---|---|
200 | Successful request. |
4xx | Client error, see Error Codes. |
5xx | Indicates an error with Nomos servers. |
Error Schema
Nomos uses standard HTTP codes to indicate the success or failure of your requests. Below is a list of possible error types you may encounter when using the Nomos API.
| Status Code | Type | Description |
|---|---|---|
400 | malformed | The request has incorrect syntax, such as an unparseable JSON body. |
401 | unauthenticated | The request doesn’t have the required credentials. |
403 | permissionDenied | The authenticated user doesn’t have permissions to perform the request. |
404 | notFound | The requested resource doesn’t exist. |
409 | conflict | The request conflicts with another request. |
422 | invalid | The request has invalid properties. |
429 | tooManyRequests | The API user has made too many requests in violation of our API Terms of Service. |
500 | internal | An unexpected error occurred and the result of the request is unknown. |
501 | notImplemented | The operation requested is not supported. |
Handling Errors
When an error occurs, the response body will contain additional information about the error. Here is an example of an error response:
Rate limit
The response headers describe your current rate limit following every request in conformance with the IETF standard:
Header name | Description |
|---|---|
ratelimit-limit | Maximum number of requests allowed within a window. |
ratelimit-remaining | How many requests you have left within the current window. |
ratelimit-reset | How many seconds until the limits are reset. |
retry-after | How many seconds you should wait before making a follow-up request. |
The maximum number of requests that users can send is 10 requests per second.
After that, you’ll hit the rate limit and receive a 429 response error code.
To prevent this, we recommend reducing the rate at which you request the API. This can be done by introducing a queue mechanism or reducing the number of concurrent requests per second. If you have specific requirements, contact support to request a rate increase.