Errors - Ruddr

The Ruddr API uses standard HTTP status codes to indicate the success or failure of a request.

Status Codes

Code	Description
`200 OK`	Everything worked as expected.
`204 No Content`	Everything worked as expected, but there is no content to return. Typical for delete requests.

Code	Description
`400 Bad Request`	The request was unacceptable due to an issue with the request format or data.
`401 Unauthorized`	The API key is missing or invalid.
`403 Forbidden`	The requested feature is not enabled for this workspace.
`404 Not Found`	The resource or endpoint does not exist.
`405 Method Not Allowed`	The endpoint URL exists, but does not support the requested operation.
`409 Conflict`	A resource with the same identifying information already exists, or the resource is read-only.
`423 Locked`	API access is disabled for this workspace. Contact support for assistance.
`429 Too Many Requests`	Rate limit exceeded. Slow down and retry after a delay.

Code	Description
`500 Internal Server Error`	Something went wrong on Ruddr’s end.

Error responses return a JSON object with a status code and descriptive message:

{
  "status": 400,
  "message": "Parameter 'id' is not a valid UUID."
}

Some validation errors may include an errors array with details:

{
  "status": 400,
  "message": "There was a problem processing your request. See errors for more details.",
  "errors": ["'name' is required"]
}