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>"
}

Subaccount API


Error ID Information Actions
validation Details:

The request failed due to validation errors

Resolution:

See the detail (and, if present, the invalid_parameters) fields for the exact reason this request was rejected and review the documentation.

View API reference
valid-transfers Details:

Invalid transfer

Resolution:

See the detail field for the reason this transfer is invalid.

View API reference
provisioning Details:

Maximum number of sub-accounts reached

Resolution:

If you need more subaccounts, contact Vonage Support.

internal-error Details:

An error has occurred in the platform while processing this request

Resolution:

If the error persists, contact Vonage Support.