Skip to main content
The Nomos API uses standardized error responses to help you quickly identify and troubleshoot issues. Nomos uses standard HTTP codes to indicate the success or failure of your requests.
  • 2xx codes correspond to success
  • 4xx codes are for user-related failures
  • 5xx codes are for infrastructure issues
Each error response includes:
  • A machine-readable code identifying the error type
  • A human-readable message explaining what went wrong
  • A docs URL linking to detailed documentation about the error
  • A unique requestId for tracking and debugging
When reporting issues, always include the requestId to help us investigate more effectively. 
{
  "error": {
    "code": "UNAUTHORIZED",
    "message": "We were unable to authorize your request.",
    "docs": "https://docs.nomos.energy/api-references/errors/UNAUTHORIZED",
    "requestId": "37a04f8f-e791-491c-81e1-86cd304649bb"
  }
}
If you can’t debug something on your own or think there is a bug, please get in touch with us on Email and provide the full error response.

​
Error Reference

​
BAD_REQUEST

Problem: The request is malformed, either missing required fields, using wrong datatypes, or being syntactically incorrect. Solution: Check if you are sending correct path params and query params.

​
UNAUTHORIZED

Problem: You are not authenticated. That means that either the credentials are expired, invalid or non existent. Solution: Check your authentication credentials and try again. Read our authentication guide for more information.

​
FORBIDDEN

Problem: We were able to authenticate you, but you don’t have permission to access this resource. Solution: Double check the resource you’re trying to access and make sure you have the necessary permissions.

​
NOT_FOUND

Problem: The resource you’re trying to access doesn’t exist. This can happen for a variety of reasons. You might be trying to access a resource that doesn’t exist or you might not have permission to access it. Solution: Double check the resource you’re trying to access and make sure you have the necessary permissions.

​
METHOD_NOT_ALLOWED

Problem: The HTTP method you used is not supported for this endpoint. Solution: Check the API documentation to see which HTTP methods are allowed for this endpoint and use the correct method.

​
CONFLICT

Problem: Another resource already uses that entry. For example emails must be unique globally. Solution: Check the request by debugging or logging it and making sure it’s correct.

​
UNPROCESSABLE_ENTITY

Problem: The request was well-formed but was unable to be followed due to semantic errors. Solution: This is an error to avoid sending invalid requests from the server to the client. If you see this error, it means that the request was malformed in some way. Please contact us via email.

​
TOO_MANY_REQUESTS

Problem: You’ve made too many requests in a given amount of time. Solution: Wait a bit and try again.

​
INTERNAL_SERVER_ERROR

Problem: An unexpected server error occurred. This is typically caused by a bug or system issue on our end. Solution: Check the request by debugging or logging it and making sure it’s correct. If that doesn’t help, write us an email.