Errors
HTTP error codes as published on developer.ringover.com, plus the OpenAPI ProblemDetails schema
HTTP status codes
| Code | Meaning |
|---|---|
400 | Bad request — invalid parameters or body |
401 | Unauthorized — invalid/expired API key, or access denied by permission/Monitoring checks on most endpoints |
402 | Payment required — feature not available on your plan |
403 | Forbidden — authenticated request refused by specific endpoint logic (notably some Empower routes) or upstream forwarded services |
404 | Resource not found |
429 | Rate limit exceeded (see Authentication) |
500 | Internal server error |
Source: Ringover API Documentation — "Error Responses".
ProblemDetails schema (from the OpenAPI)
Where an operation documents application/problem+json (mainly SCIM routes today), the body follows this shape:
{
"type": "https://docs.ringover.com/errors/not_found",
"title": "Not Found",
"status": 404,
"detail": "profile not found",
"code": "not_found",
"trace_id": "4bf92f3577b34da6a3ce929d0e0e4736"
}| Property | Description |
|---|---|
type | URI reference to documentation for the error (default about:blank) |
title | Short, human-readable summary |
status | HTTP status code |
detail | Explanation specific to this occurrence |
code | Stable machine-readable error code (snake_case) |
trace_id | W3C trace id, present when the call was sampled |
instance | URI reference identifying the specific occurrence |
errors | Optional list of field-level error details |
Not universal
Most non-SCIM operations only document plain status codes with a short text description (see the table above) rather than a structured JSON body. Check the specific operation in the API Reference.