Errores de API

Cuando una API de Vonage devuelve un error, por ejemplo, si tu Account no tiene crédito, la API devolverá un error en formato RFC 7807.

Esto proporciona una explicación básica de cuál es el problema, por qué se produjo y los pasos para resolverlo. Echa un vistazo al ejemplo para ver cómo se formatea un fuera de crédito.

En esta página encontrará una lista de todos los posibles errores que pueden producirse, junto con una explicación más detallada de cómo solucionarlos.

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

Errores genéricos

Código	Información	Acciones
`low-balance`	Descripción This request could not be performed due to your account balance being low. Resolución Top up your account in the Vonage Dashboard
`unauthorized`	Descripción You did not provide correct credentials. Resolución Check your authentication credentials are correct, you can find these credentials in the Vonage Dashboard
`forbidden`	Descripción Your account does not have permission to perform this action Resolución Check that you're using the correct credentials, and that your account has this feature enabled
`not-found`	Descripción The requested resource does not exist, or you do not have access to it Resolución Check both the URI that you're requesting and your authentication credentials
`unprovisioned`	Descripción The credentials provided do not have access to the requested product Resolución Check your API key is correct and has been whitelisted
`account-suspended`	Descripción This account has been suspended Resolución Contact support for more information
`jwt-expired`	Descripción The JWT provided has expired Resolución Generate a new JWT with an `exp` in the future
`jwt-revoked`	Descripción The JWT provided has been revoked Resolución Generate a new JWT using your private key
`invalid-api-key`	Descripción The API key provided does not exist in our system, or you do not have access Resolución Modify your request to provide a valid API key
`invalid-params`	Descripción The value of one or more parameters is invalid Resolución Resend a valid request body
`invalid-signature`	Descripción The signature provided did not validate. Resolución Check your signature secret is correct and you're following the correct signing process
`invalid-ip`	Descripción The source IP address of the request is not in our allow list Resolución Make a request from an allowed IP address, or add your current IP to the list of authorized addresses
`multiple-auth-methods`	Descripción Multiple authentication methods were detected in your request Resolución Provide exactly one authentication method
`invalid-id`	Descripción The ID provided does not exist in our system Resolución Modify your request to provide a valid ID
`invalid-json`	Descripción The request body did not contain valid JSON Resolución Send a JSON request body, including a Content-Type header of application/json
`throttled`	Descripción You have hit the rate limit for the API Resolución Retry the request after waiting (differs per API)
`wrong-verb`	Descripción This endpoint does not support the HTTP verb that you requested Resolución Read the API documentation to see which verbs your desired endpoint supports
`accept-header`	Descripción Invalid Accept header provided Resolución Most Vonage APIs only send back application/json. Check the API documentation for the API that you're working with for a complete list of supported data types
`content-type-header`	Descripción Invalid Content-Type header provided Resolución Most Vonage APIs only accept application/json. Check the API documentation for the API that you're working with for a complete list of supported data types
`unavailable-legal`	Descripción Unavailable For Legal Reasons Resolución Vonage APIs are unavailable in the following areas due to international sanctions Sudan Syria Crimea North Korea Iran Cuba
`application-suspended`	Descripción This application has been suspended Resolución Re-enable the application or create a new application to use

Errores específicos del producto

SMS API

Código	Información
`1`	Descripción Throttled. You are sending SMS faster than the account limit. Resolución Refer to What is the Throughput Limit for Outbound SMS? for more information.
`2`	Descripción Missing Parameters. Your request is missing one of the required parameters `from`, `to`, `api_key`, `api_secret` or `text`. Resolución Check your parameters and try again.
`3`	Descripción Invalid Parameters. The value of one or more parameters is invalid. Resolución Check your parameters and try again.
`4`	Descripción Invalid Credentials. Your API key and/or secret are incorrect, invalid or disabled. Resolución Visit the Dashboard and check your credentials.
`5`	Descripción Internal Error. An error has occurred in the platform whilst processing this message. Resolución If the error persists, contact support.
`6`	Descripción Invalid Message. The platform was unable to process this message, for example, an un-recognized number prefix. Resolución N/A
`7`	Descripción Number Barred. The number you are trying to send messages to is blacklisted and may not receive them. Resolución N/A
`8`	Descripción Partner Account Barred. Your Vonage account has been suspended. Resolución Contact support.
`9`	Descripción Partner Quota Violation. You do not have sufficient credit to send the message. Resolución Top-up and retry.
`10`	Descripción Too Many Existing Binds. The number of simultaneous connections to the platform exceeds your account allocation. Resolución Back-off and retry.
`11`	Descripción Account Not Enabled For HTTP. This account is not provisioned for the SMS API. Resolución This error usually indicates that you should use SMPP instead.
`12`	Descripción Message Too Long. The message length exceeds the maximum allowed. Resolución Send shorter messages.
`14`	Descripción Invalid Signature. The signature supplied could not be verified. Resolución Check the documentation for signing messages or use one of the SDKs to handle the signing.
`15`	Descripción Invalid Sender Address. You are using a non-authorized sender ID in the `from` field. Resolución This is most commonly seen in North America, where a Vonage long virtual number or short code is required.
`17`	Descripción Message Blocked by Provider. The messaging provider has chosen to block this message. This may be due to content or restrictions imposed by the provider. Resolución N/A
`22`	Descripción Invalid Network Code. The network code supplied was either not recognized, or does not match the country of the destination address. Resolución Check the network code or remove it from your request.
`23`	Descripción Invalid Callback Url. The callback URL supplied was either too long or contained illegal characters. Resolución Supply a valid URL for the callback.
`29`	Descripción Non-Whitelisted Destination. Your Vonage account is still in demo mode. While in demo mode you must add target numbers to your whitelisted destination list. Resolución Top-up your account to remove this limitation.
`32`	Descripción Signature And API Secret Disallowed. A signed request may not also present an `api_secret`. Resolución Remove the API secret from your request, or don't sign the message.
`33`	Descripción Number De-activated. The number you are trying to send messages to is de-activated and may not receive them. Resolución N/A

Redact API

Código Información Acciones

Código	Información	Acciones
`invalid-product`	Descripción The provided product is invalid Resolución Modify your request to provide a valid product
`premature-redaction`	Descripción There is a 1 hour time period before data can be redacted to allow for all data to propagate through the Vonage system Resolución Wait until the data becomes valid for redaction
`rate-limit`	Descripción The request was rate limited Resolución The Redact API supports 170 requests per second. Slow down your request rate

invalid-product

Descripción

The provided product is invalid

Resolución

Modify your request to provide a valid product

premature-redaction

Descripción

There is a 1 hour time period before data can be redacted to allow for all data to propagate through the Vonage system

Resolución

Wait until the data becomes valid for redaction

rate-limit

Descripción

The request was rate limited

Resolución

The Redact API supports 170 requests per second. Slow down your request rate

API de Account

Código Información Acciones

Código	Información	Acciones
`validation`	Descripción The provided payload is invalid Resolución Modify your request to provide a valid payload. Minimum 8 characters Maximum 25 characters Minimum 1 lower case character Minimum 1 upper case character Minimum 1 digit
`delete-last-secret`	Descripción You can not delete your only API secret Resolución Add another API secret before deleting this one

validation

Descripción

The provided payload is invalid

Resolución

Modify your request to provide a valid payload.

Minimum 8 characters
Maximum 25 characters
Minimum 1 lower case character
Minimum 1 upper case character
Minimum 1 digit

delete-last-secret

Descripción

You can not delete your only API secret

Resolución

Add another API secret before deleting this one

API de subcuentas

Código	Información	Acciones
`validation`	Descripción The request failed due to validation errors Resolución See the `detail` (and, if present, the `invalid_parameters`) fields for the exact reason this request was rejected and review the documentation.
`invalid-transfers`	Descripción Invalid transfer Resolución See the `detail` field for the reason this transfer is invalid.
`provisioning`	Descripción Maximum number of sub-accounts reached Resolución If you need more subaccounts, contact Vonage Support.
`internal-error`	Descripción An error has occurred in the platform while processing this request Resolución If the error persists, contact Vonage Support.
`invalid-number-transfer`	Descripción Failed to perform transfer number from source account to destination account Resolución See the `detail` field for the reason this transfer is invalid.
`missing-number-transfer`	Descripción Could not transfer number from source account to destination account - ShortCode not found Resolución See the `detail` field for the reason this transfer is invalid.
`transfer-conflict`	Descripción Could not transfer number from source account to destination account - ShortCode is already owned by requesting account Resolución See the `detail` field for the reason this transfer is invalid.

API de aplicaciones

Código Información Acciones

Código	Información	Acciones
`payload-validation`	Descripción Invalid request. See `invalid_parameters` field for details Resolución Review the documentation and send a valid `POST` request.
`list-validation`	Descripción Invalid request. See `invalid_parameters` field for details Resolución Review the documentation and send a valid `GET` request.
`rate-limit`	Descripción The request was rate limited Resolución The Redact API supports 170 requests per second. Reduce the frequency of your requests.

payload-validation

Descripción

Invalid request. See invalid_parameters field for details

Resolución

Review the documentation and send a valid POST request.

list-validation

Descripción

Invalid request. See invalid_parameters field for details

Resolución

Review the documentation and send a valid GET request.

rate-limit

Descripción

The request was rate limited

Resolución

The Redact API supports 170 requests per second. Reduce the frequency of your requests.

Messages API

Código	Información
`1000`	Throttled - You have exceeded the submission capacity allowed on this account. Please wait and retry
`1010`	Missing params - Your request is incomplete and missing some mandatory parameters.
`1020`	Invalid params - The value of one or more parameters is invalid.
`1021`	Invalid tag - The tag value is invalid.
`1022`	Invalid template - Invalid template or template parameters
`1030`	Internal error - There was an error processing your request in the Platform.
`1040`	Invalid message - The Platform was unable to process your request. For example, due to an unrecognised prefix for the phone number.
`1050`	Number barred - The number you are trying to submit to is blacklisted and may not receive messages.
`1060`	Partner account barred - The `api_key` you supplied is for an account that has been barred from submitting messages.
`1070`	Partner quota exceeded - Your pre-paid account does not have sufficient credit to process this message.
`1080`	Account not enabled for REST - This account is not provisioned for REST submission, you should use SMPP on the SMS API.
`1090`	Message too long - The length of `udh` and `body` was greater than 140 octets for a binary type SMS request.
`1100`	Communication Failed - Message was not submitted because there was a communication failure.
`1120`	Illegal Sender Address - rejected - Due to local regulations, the `SenderID` you set in from in the request was not accepted. Please check the Global messaging section.
`1130`	Invalid TTL - The value of `ttl` in your request was invalid.
`1140`	Facility not allowed - Your request makes use of a facility that is not enabled on your account.
`1150`	Invalid Message class - The value of `message-`class in your request was out of range. See https://en.wikipedia.org/wiki/Data_Coding_Scheme.
`1160`	Non White-listed Destination - The phone number you set in to is not in your pre-approved destination list. To send messages to this phone number, add it using Dashboard.
`1170`	Invalid or Missing Msisdn Param - The phone number you supplied in the to parameter of your request was either missing or invalid.
`1180`	Absent Subscriber Temporary - This message was not delivered because to was temporarily unavailable. For example, the handset used for to was out of coverage or switched off. This is a temporary failure, retry later for a positive result.
`1190`	Absent Subscriber Permanent - `to` is no longer active, You should remove this phone number from your database.
`1200`	Portability Error - There is an issue after the user has changed carrier for to. If the user wants to receive messages from you, they need to contact their carrier directly.
`1210`	Anti-Spam Rejection - Carriers often apply restrictions that block messages following different criteria. For example on SenderID or message content.
`1220`	Handset Busy - The handset associated with to was not available when this message was sent. If status is rejected, this is a temporary failure; retry later for a positive result. If status is submitted, this message has is in the retry scheme and will be resent until it expires in 24-48 hours.
`1230`	Network Error - A network failure while sending your message. This is a temporary failure, retry later for a positive result.
`1240`	Illegal Number - You tried to send a message to a blacklisted phone number. That is, the user has already sent a STOP opt-out message and no longer wishes to receive messages from you.
`1241`	Too many send requests - Too many send requests to phone numbers.
`1242`	Number pool does not exists - check that the number pool has been configured for your account
`1250`	Unroutable - The chosen route to send your message is not available. This is because the phone number is either currently on an unsupported network or on a pre-paid or reseller account that could not receive a message.
`1251`	Unable to route traffic to a destination - This may be due to the routing rules applied for your destination network.
`1260`	Destination unreachable - The message could not be delivered to the phone number. If using Viber Business Messages your account might not be enabled for this country.
`1270`	Subscriber Age Restriction - The carrier blocked this message because the content is not suitable for to based on age restrictions.
`1280`	Number Blocked by Carrier - The carrier blocked this message. This could be due to several reasons. For example, to's plan does not include SMS or the account is suspended.
`1282`	Message blocked by provider - The messaging provider has chosen to block this message. This may be due to content or restrictions imposed by the provider.
`1290`	Pre-Paid - Insufficient funds - to’s pre-paid account does not have enough credit to receive the message.
`1300`	Not part of the provider network - The number or ID is not a user in the provider network.
`1310`	Not suitable device - The user's device can't receive the message.
`1320`	Message already sent - The message was already sent.
`1330`	Unknown - An unknown error was received from the carrier who tried to send this this message. Depending on the carrier, that to is unknown. When you see this error, and status is rejected, always check if to in your request was valid.
`1331`	Provider error - The provider is not responding or unable to process the request. Please try sending your message in a few minutes time.
`1340`	Outside of the allowed window - This message is sent outside of allowed response window.
`1350`	Phone matching fee not paid - Requires phone matching access fee to be paid by the Facebook Page.
`1360`	TTL was activated, or message expired before delivered.
`1370`	Expired access Token - Please reauthenticate your Facebook Page with Vonage.
`1380`	Invalid resource - Please check that the URL your provided to your resource is accessible and valid.
`1381`	Resource size is too large - Please try sending a smaller media file.
`1382`	Resource type is invalid - Please check that the file you are trying to send is valid.
`1400`	Unsupported channel - The channel specified in the request is not supported.
`1410`	Invalid channel parameters - The value of one or more parameters is invalid.
`1420`	Invalid sender - The `from` parameter is invalid for the given channel.
`1430`	Invalid recipient - The `to` parameter is invalid for the given channel.
`1440`	Invalid message type - The message type specified in the request is not supported for the given channel.
`1450`	Invalid client reference - The client reference can be a string of up to 100 characters.
`1451`	Invalid context - the reference to the original message could not be found because it is invalid or no longer available.
`1460`	Daily message limit exceeded - Check compliance with regulations such as 10DLC.
`1461`	Auto-limiting of messages by Provider - This message was not delivered by Provider to avoid excessive messages to the end user. For details please see this knowledgebase article.
`1470`	Fraud Defender Traffic Rule - Rejected due to Fraud Defender traffic rules block.
`1472`	Fraud Defender SMS Burst Protection - Traffic limit has been reached
`1473`	AIT Protection - The message has been rejected by Fraud Defender AIT Protection
`1474`	Fraud Defender Traffic Rule - Rejected due to Fraud Defender country block.
`1475`	Fraud Defender Traffic Rule - Rejected due to Fraud Defender network block.
`1480`	Entity Filter - The message failed due to `entity_id` being incorrect or not provided. More information on country specific regulations.
`1481`	Header Filter - The message failed because the header ID (`from` phone number) was incorrect or missing. More information on country specific regulations.
`1482`	Content Filter - The message failed due to `content_id` being incorrect or not provided. More information on country specific regulations.
`1483`	Consent Filter - The message failed due to consent not being authorized. More information on country specific regulations.
`1484`	Regulation Error - Unexpected regulation error - contact support.

Reports API

Código Información Acciones

Código	Información	Acciones
`invalid-request-parameters`	Descripción The provided payload is invalid Resolución Modify your request to provide a valid payload
`invalid-abort-operation`	Descripción The job is already in a terminated state such as `SUCCESS`, `TRUNCATED`, `FAILED` or `ABORTED`. Resolución None
`rate-limit`	Descripción The request was rate limited. Resolución The Reports API supports 5 requests per second when used Asynchronously, and 10 requests per second Synchronously. Slow down your request rate.

invalid-request-parameters

Descripción

The provided payload is invalid

Resolución

Modify your request to provide a valid payload

invalid-abort-operation

Descripción

The job is already in a terminated state such as SUCCESS, TRUNCATED, FAILED or ABORTED.

Resolución

None

rate-limit

Descripción

The request was rate limited.

Resolución

The Reports API supports 5 requests per second when used Asynchronously, and 10 requests per second Synchronously. Slow down your request rate.

Aprovisionamiento de WhatsApp

Código	Información
`number-in-use`	Descripción Cannot use number because it's already in use by another deployment. Resolución Use the existing deployment.
`invalid-json`	Descripción The request body did not contain valid JSON Resolución Send a JSON request body, including a Content-Type header of application/json
`unprocessable`	Descripción Parameters were valid JSON but something was missing or wrongly formatted Resolución Fix the incorrect request parameters and try again
`unprocessable-profile-update`	Descripción Parameters were valid JSON but something was missing or wrongly formatted Resolución Fix the incorrect request parameters and try again
`throttled`	Descripción Too many requests have been made on this endpoint Resolución Wait a moment and try again
`verification-failed`	Descripción Verification step failed. Either because the provided code was incorrect or because too many attempts have been made Resolución Try again with the correct OTP, or call resend-otp
`conflict-deployment-state`	Descripción Deployment could not be modified because it is currently in a transitional state. Resolución If the deployment is transitioning into the state you want it in no action is required. If the state is `DELETING`, no action is required as the deployment will be deleted. Otherwise, wait for the transition to complete and try again.
`conflict-resend-otp`	Descripción Could not resend OTP because the current state of the deployment did not allow it Resolución The deployment has either already finished, or is in an error state (in which case you should delete it and run it again).

10 DLC API

Código	Información
`brand-conflict`	Descripción A conflict when a brand is being created or edited and there is an issue with a 3rd party vendor. Resolución Ensure all required fields have values and there are no errors in those values. If the error persists, contact support.
`brand-parameters`	Descripción There are errors in the brand data submitted. Resolución Ensure all required fields have values included and correct any errors to values in the specified fields.
`invalid-usecase-data`	Descripción There are errors in the data submitted for use case qualification. Resolución Ensure all required fields have values included and correct any errors to values in the specified fields.
`use-case-denied`	Descripción The use case requested has been denied for this brand. Resolución Ensure your use case does not require additional brand vetting or pre/post Mobile Network Operator approval.
`vetting-conflict`	Descripción A conflict during the brand vetting request has occurred. Resolución If the error persists, contact support.
`invalid-vetting-data`	Descripción There are errors in the vetting request data submitted. Resolución Ensure all required fields have values and correct any errors to values in the specified fields.
`invalid-json`	Descripción Your request cannot be parsed. Resolución Ensure there are no invalid characters or values in your request.
`brand-not-qualified`	Descripción A conflict when a campaign is being created under a brand that hasn't qualified for the specified use case. Resolución Verify the brand use case qualifies before submitting the campaign.
`invalid-campaign-data`	Descripción There are errors in the campaign data submitted. Resolución Ensure all required fields have values and correct any errors to values in the specified fields.
`numbers-already-linked`	Descripción The number you are attempting to link is already linked to another campaign. Resolución You must link a unique number to a campaign. Link a different number to this campaign.
`invalid-number-data`	Descripción There are errors in the number data submitted. Resolución Ensure all required fields have values and correct any errors to values in the specified fields.

Conversation API

Código	Información
`device:error:invalid`	The request failed due to incorrect device parameters.
`device:error:not-found`	The request failed due to unknown device.
`device:error:max-device-limit`	The request failed due to registered devices exceeding max devices limit per user
`session:error:internal`	An internal error occurred with the session. Please try again shortly.
`session:error:invalid-event`
`session:error:not-found`	Session does not exist, or you do not have access.
`session:error:bad-request-ttl`	The request cannot be processed due to malformed ttl.
`session:error:max-open-sessions`	The maximum amount of open sessions has been established. Please delete them by logging out and try again.
`knocking:error:not-found`	Knocker does not exist, or you do not have access.
`knocking:error:invalid`	The current knocker could not be processed. This can be due to an invalid state or an invalid channel type.
`knocking:error:invalid-channel`	The request failed due to either malformed or missing channel. Please provide a valid channel and try again.
`knocking:error:missing-from-name`	The request failed due to missing 'from' user. Please provide a valid user and try again.
`knocking:error:legs-not-match`	The leg id in knocker doesn't match the leg to join. Please provide a valid leg id.
`application:error:internal`	An internal error occurred with the application. Please try again shortly.
`application:error:invalid-event`	Application event does not exist, or you do not have access.
`application:error:not-found`	Application does not exist, or you do not have access.
`application:error:permission-denied`	Permission denied
`conversation:error:bad-request`	The request failed due to validation errors. Please provide a valid request and try again.
`conversation:error:invalid-action`	The request failed because the current action is not valid. Please provide a valid action and try again.
`conversation:error:not-allowed`	The request failed because the current state of the conversation is INACTIVE. Only GET and DELETE actions are allowed.
`conversation:error:duplicate-name`	The request failed because the conversation name already exists. Please provide a unique conversation name and try again.
`conversation:error:internal`	An internal error occurred with the conversation. Please try again shortly.
`conversation:error:internal-media`	An internal error occurred with the conversation media. Please try again shortly.
`conversation:error:invalid-channel`	The request failed due to either malformed or missing channel. Please provide a valid channel and try again.
`conversation:error:invalid-member`	The request failed due to an invalid member. Please provide a valid member and try again.
`conversation:error:invalid-member-state`	The conversation membership has already ended
`conversation:error:member-already-joined`	The request failed due to the user already having a member joined with that channel content. Please provide a valid user and try again.
`conversation:error:member-already-invited`	The request failed due to the user already having a member invited with that channel content. Please provide a valid user and try again.
`conversation:error:member-not-found`	Member does not exist, or you do not have access.
`conversation:error:invalid-event`	The request failed due to an invalid conversation event. Please provide a valid event and try again.
`conversation:error:not-found`	Conversation does not exist, or you do not have access.
`conversation:error:permission-denied`	expired JWT, invalid application.
`conversation:error:maximum-number-of-members`	The request failed due to the maximum number of joined/invited members in the conversation. Please reduce the number of members and try again.
`conversation:error:member:permission-denied`	You did not provide a correct token. Please provide a valid token.
`conversation:error:member:channel-not-found`	The request failed due to a non-existent requested channel. Please provide a valid channel id/number and try again.
`user:error:invalid-event`	The request failed due to an invalid user event. Please provide a valid event and try again.
`user:error:duplicate-name`	The request failed because the user name already exists. Please provide a unique user name and try again.
`user:error:internal`	An internal error occurred with the user. Please try again shortly.
`user:error:invalid-state-lookup`	The request failed due to an invalid member state filter value. Please provide a valid state name and try again.
`user:error:not-found`	User does not exist, or you do not have access.
`user:error:invalid-user`	The request failed due to an invalid user name. Please provide a valid user name and try again.
`user:error:invalid-user-token`	Token does not contain a user name.
`user:error:invalid-user-name`	Username must not be 'me' and it must not start with 'USR-'.
`user:error:invalid-application`	Application does not exist, or you do not have access.
`user:notification:error:not-found`	Notification does not exist, or you do not have access.
`user:device:error:not-found`	The request failed due to non-existent user devices. Please register a device and try again.
`event:error:internal`	An internal error occurred with the event. Please try again shortly.
`event:error:bad-request`	The request failed due to an invalid event. Please provide a valid event and try again.
`event:error:unknown-event`	The request failed due to an unknown event. Please provide a known event and try again.
`event:error:not-found`	Event does not exist, or you do not have access.
`event:error:not-joined`	The request failed due to the member not being in a 'JOINED' state. Please update the member state and try again.
`event:error:permission-denied`	You do not have access to the event.
`event:error:invalid-filter-group`	The request failed due to an invalid filtering.
`event:error:delete-not-allowed`	The request failed because the event is not allowed to be deleted. Only message and custom events are allowed.
`text:error:unknown-event`	The request failed due to an unknown text event. Please provide a known text event and try again.
`text:error:permission-denied`	You do not have access to the text event.
`text:error:invalid-member`	The request failed due to an invalid member. Please provide a valid member and try again.
`text:error:not-joined`	The request failed due to the member not being in a 'JOINED' state. Please update the member state and try again.
`image:error:unknown-event`	The request failed due to an unknown image event. Please provide a known image event and try again.
`image:error:permission-denied`	You do not have access to the image.
`image:error:invalid-member`	The request failed due to an invalid member. Please provide a valid member and try again.
`image:error:not-joined`	The request failed due to the member not being in a 'JOINED' state. Please update the member state and try again.
`rtc:error:invalid-event`	The request failed due to an invalid RTC event. Please provide a valid RTC event and try again.
`rtc:error:invalid-member`	The request failed due to an invalid member. Please provide a valid member and try again.
`rtc:error:ice:failed`	The request failed due to an invalid ICE candidate. Please provide a valid ICE candidate and try again.
`rtc:error:missing-id`	The request failed due to an invalid RTC id. Please provide a valid RTC id and try again.
`rtc:error:permission-denied`	You do not have access to the RTC object.
`rtc:error:unprocessable`	The request failed because the RTC content could not be processed. Please provide valid RTC content and try again.
`rtc:error:internal`	An internal error occurred with the RTC object. Please try again shortly.
`rtc:error:not-joined`	The request failed due to the member not being in a 'JOINED' state. Please update the member state and try again.
`leg:error:db`	A database error occurred with the conversation leg. Please try again shortly.
`leg:error:invalid-action`	The request failed due to an invalid leg action. Please provide a valid leg action and try again.
`leg:error:internal`	An internal error occurred with the conversation leg. Please try again shortly.
`leg:error:not-found`	Conversation leg does not exist, or you do not have access.
`leg:error:not-answered`	The request failed due to the leg not being in an 'answered' state. Please update the leg state and try again.
`leg:error:invalid-event`	The request failed due to an invalid leg event. Please provide a valid leg event and try again.
`leg:error:invalid-application`	Application does not exist, or you do not have access.
`leg:error:conversation-not-found`	Request failed due to leg not being linked to an active conversation
`leg:error:complete`	The request failed due to the leg being in a completed state and as a result no further action can be taken.
`audio:error:not-found`	Audio request does not exist, or you do not have access.
`audio:error:invalid-event`	The request failed due to an invalid audio event. Please provide a valid audio event and try again.
`system:error:permission`	You did not provide a correct token. Please provide a valid token.
`system:error:missing-token`	You did not provide a token. Please provide a valid token.
`system:error:invalid-token`	You did not provide a valid token. Please provide a valid token.
`system:error:expired-token`	You provided an expired token. Please provide a valid token.
`system:error:internal`	An internal error occurred. Please try again shortly.
`system:error:invalid-event`	The request failed due to an invalid event. Please provide a valid event and try again.
`http:error:not-found`	Endpoint does not exist, or you do not have access.
`http:error:method-not-allowed`	Request method not supported.
`http:error:version-not-allowed`	The request failed due to an invalid endpoint version. Please provide a valid endpoint version and try again.
`http:error:unsupported-media-type`	Invalid media type provided.
`http:error:internal`	An internal error occurred. Please try again shortly.
`media:error:not-found`	Media does not exist, or you do not have access.
`media:error:too-many-request`	You have exceeded your media request limit. You can try again shortly.
`media:error:internal`	An internal error occurred with the media object. Please try again shortly.
`media:error:leg-already-answered`	The request failed because the leg was already answered
`media:error:bad-request`	The request failed due to an invalid media request. Please provide a valid media request and try again.
`paginator-builder:error:invalid-cursor`	The request failed due to an invalid cursor
`asr:error:max-duration`	The request failed due to invalid range for the max_duration param. Please specify a range between 1 and 40.
`asr:error:start-timeout`	The request failed due to invalid range for the start_timeout param. Please specify a range between 1 and 10.
`custom-data:error:max-data-limit`	The request failed due to custom data exceeding max data limit
`custom-data:error:max-data-sum-limit-exceeded`	The request failed due to the sum of custom data exceeded max data limit
`ephemeral:error:max-data-limit`	The request failed due to ephemeral data exceeding max data limit
`http:error:validation-fail`	Input validation failure.
`http:error:invalid-content-type`	Invalid Content-Type.
`message:error:invalid-event`	The request failed due to an invalid message event. Please provide a valid event and try again.
`message:error:user-undefined`	The request failed due to an undefined user. Please provide a user and try again.
`message:error:conversation-name-undefined`	The request failed due to an undefined conversation_name. Please provide a conversation_name and try again.
`message:error:permission-denied`	You do not have access to the message.
`message:error:invalid-member`	The request failed due to an invalid member. Please provide a valid member and try again.
`message:error:not-joined`	The request failed due to the member not being in a 'JOINED' state. Please update the member state and try again.
`message:error:permission`	Request header 'Authorization' missing / Invalid Token.
`message:error:not-found`	External id does not exist, or you do not have access.
`message:error:channel-unknown`	The request failed due to an unknown channel type. Please provide a known channel and try again.
`message:error:message-type-unknown`	The request failed due to an unknown message type. Please provide a known message and try again.
`nexmo-service:permission-denied`	You did not provide a correct token. Please provide a valid token.
`nexmo-service:error:invalid-event`	The request failed due to an invalid nexmo-service event. Please provide a valid event and try again.
`nexmo-service:error:datacenter-not-found`	Datacenter id does not exist, or you do not have access.

pages.apiErrors.products.traffic-control

Código	Información
`throttled`	Your request rate exceeds the allowed limit for this account.
`internal-error`	An internal error occurred. Please try again later.
`invalid-product`	Path parameter `product_name` didn't validate. The given product is not supported.
`invalid-provisioner-command`	The path segment denoting the action to be performed is not valid. The only allowed actions are `/activate` and `/deactivate`.
`invalid-date-format`	Invalid date format. Please provide the `start_date` and `end_date` in ISO8601 format.
`missing-query-param`	One or more required query parameters was not specified.

API Verify.V2

Código	Información
`fragment-exists`	Descripción A template fragment for this channel and locale already exists Resolución Change either the locale or channel to a combination not being used
`template-fragment-not-found`	Descripción Template Fragment not found Resolución Check the ID of the template fragment you are trying to access
`template-not-found`	Descripción Template not found Resolución Check the ID of the template you are trying to access
`template-exists`	Descripción A template with this name already exists Resolución Choose a different template name in the request
`not-empty-template`	Descripción The template is not empty and cannot be deleted. Please delete its fragments first Resolución Delete the individual template fragments, then try again
`forbidden`	Descripción Templates management is not enabled for your account Resolución Contact Vonage support to enable custom template management
`expired`	Descripción An incorrect code has been provided too many times. Workflow terminated. Resolución Request a new Verification
`no-code`	Descripción The current Verify workflow step does not support a code. Resolución Change to a valid workflow to handle your request
`max-templates`	Descripción An account can only have a maximum of 10 custom templates Resolución Delete a template before retrying
`concurrent`	Descripción Concurrent verifications to the same number are not allowed. Resolución In flight verification needs to expire, fail or be completed
`invalid-code`	Descripción The code you provided does not match the expected value. Resolución Retry with the correct value or fail the request
`no-events`	Descripción The code you provided does not match the expected value. Resolución Retry with the correct value or fail the request
`request-not-found`	Descripción The request ID provided could not be found. Resolución Retry with a valid request ID
`msisdn-error`	Descripción The device MSISDN does not match. Resolución Silent Auth will not work with this device, try a different one.
`precondition-failed`	Descripción Conditions for the Silent Auth request to complete have not been met. Resolución Silent Auth will not work with this device, try a different one.
`network-error`	Descripción The Silent Auth request could not be completed due to formatting or the carrier is not supported. Resolución Check https://developer.vonage.com/en/verify/guides/silent-auth-territories?source=verify to see if the carrier(s) used are supported.

Defensor del Fraude API

Código	Información
`http:error:conflict`	Rule couldn't be added as conflicts with currently existing rules
`system:error:internal-error`	Something went wrong.
`http:error:validation-fail`	There was an issue when validating fields. Please refer to the API specs
`http:error:bad-request`	Bad Request. Please refer to the API specs