View all errors
API Errors
When a Nexmo API returns an error, for instance, if your account has no credit, the API will return an error in RFC 7807 format.
This provides a basic explanation of what the issue is, why it occurred and steps to resolve it. Check out the example to see how an out-of-credit
is formatted.
You'll likely want to consider up-front what errors your application will need to handle, this page provides a list of all the possible errors that could occur with a more detailed explanation of how they can be addressed.
HTTP/1.1 403 Forbidden
Content-Type: application/problem+json
Content-Language: en
{
"type": "https://example.com/Error#out-of-credit",
"title": "You do not have enough credit",
"detail": "Your current balance is 30, but that costs 50.",
"instance": "<trace_id>"
}
Redact API
Error ID | Information | Actions |
---|---|---|
invalid-product |
Details:
The provided product is invalid Resolution:Modify your request to provide a valid product |
View API reference |
premature-redaction |
Details:
There is a 1 hour time period before data can be redacted to allow for all data to propagate through the Vonage system Resolution:Wait until the data becomes valid for redaction |
|
rate-limit |
Details:
The request was rate limited Resolution:The Redact API supports 170 requests per second. Slow down your request rate |