Skip to main content

Error Codes

Last updated: 12 December 2024
info

The list of errors can be extended. Keep this in mind when setting up the integration.

Message Sending Error Codes​

Error codes after calling the api/cascade/schedule method

File IconSending Messages
CodeErrorDescription
400requestId-is-not-uniqueThis request ID has already been used. Use a new ID for each request.
400content-not-specifiedThe content type and its properties are not specified.
400contentType-not-specifiedThe content type is not specified. For example, text or image.
400text-not-specifiedThe text field is not filled in.
400caption-not-specifiedThe signature text field is not filled in.
400action-not-specifiedNo action is specified for the button.
400attachmentName-not-specified The name of the attached document is not specified.
400attachmentName-is-too-longThe name of the attached document is too long. The maximum length is 70 characters.
400latitude-not-specified Latitude is not set when specifying coordinates.
400longitude-not-specifiedThe longitude is not set when specifying coordinates.
400cascade-not-found Invalid cascade ID is specified. Request a list of all cascades of your account and check the correctness of the identifier you specified.
400request-doesn’t-contain-content-for-all-cascade-stagesThe cascade contains many channels. Add another channel to the 'content` object of the request.
400matched-template-not-foundThe schema of the request body does not match the schema of the template. Check the relative location and availability of all the properties of the request.
400cascade-scheduling-request-is-not-validThe transmitted content for the cascade does not match the cascade settings. The edna Pulse program performs an additional cascade check when a request is received to send a message using the cascade/schedule method.

If the received request does not match the cascade parameters, an error is returned with explanations in the detail field. Read the explanations to identify and resolve the discrepancy, or send a request to edna support.

400template-parameter-is-not-validThe length of the values of the ListPicker.sections.items.title or ListPicker.sections.items.subtitle parameters exceeds 24 characters, including spaces.
400out-of-balanceInsufficient funds in the balance.
400button-validation-errorError validating the WhatsApp template with buttons.

Occurs if the maximum allowed number of buttons is exceeded in the WhatsApp template.

Possible comments:

- Too many buttons, maximum is 10 — Too many buttons. The maximum number is 10.

- Too many URL buttons, maximum is 2 — Too many link buttons. The maximum number is 2.

- Too many PHONE buttons, maximum is 1 — Too many call buttons. The maximum number is 1.

- Payload is too long, maximum is 128 — The length of the payload quick response button code field has been exceeded, the maximum number of characters is 128.
401auth—errorAuthorization error. Check the spelling and the validity period of the API key.
404not-foundThe requested URL was not found. Check that the address you provided is correct.
405method-not-allowedThe HTTP request method is not allowed. Use POST, GET and other requests according to the documentation.
500system-errorServer error. Send a request to edna support.

An error may occur if the request is incorrect. Check the relative location, availability, and completeness of all request properties according to the documentation.

Examples of Cascade Checking Errors​

The content object contains channel parameters that are not present in the cascade​

Request​

In the request below, the error is caused by the smscontent parameter, since the cascade with cascadeId = 31634 includes only Viber and WhatsApp channels.

curl --location 'http://app.edna.io/api/cascade/schedule' \
--header 'Content-Type: application/json' \
--header 'x-api-key: ************' \
--data '{
    "requestId": "e62b4736-1278-4119-8816-3f2257eec47c",
    "cascadeId": 31634,
    "subscriberFilter": {
        "address": "+35700000000",
        "type": "PHONE"
    },
    "content": {
        "viberContent": {
            "contentType": "TEXT",
            "text": "cascade viber  --> whatsapp "
        },
        "whatsappContent": {
            "contentType": "TEXT",
            "text": "cascade viber  --> whatsapp"
        },
        "smsContent": {
            "contentType": "TEXT",
            "text": "cascade viber  --> whatsapp"
        }
    }
}'

Reaponse​

{
    "title": "cascade-scheduling-request-not-valid",
    "status": 400,
    "detail": "Cascade scheduling request is not valid. Violations: the cascade template stage was not found for the content [cascadeTemplateId:31,634;contentChannelType:SMS]"
}

There are no channel parameters in the content object, which is present in the cascade​

Request​

Only the viberContent parameter is passed in the request, although the cascade with cascadeId = 31634 includes Viber and WhatsApp channels.

curl --location 'http://app.edna.io/api/cascade/schedule' \
--header 'Content-Type: application/json' \
--header 'x-api-key: ****************' \
--data '{
    "requestId": "7c42344c-aeea-41c9-834b-eb627136f400",
    "cascadeId": 31634,
    "subscriberFilter": {
        "address": "+35700000999",
        "type": "PHONE"
    },
    "content": {
        "viberContent": {
            "contentType": "TEXT",
            "text": "cascade viber  --> whatsapp. No whatsapp content"
        }
    }
}'

Reaponse​

{
    "title": "cascade-scheduling-request-not-valid",
    "status": 400,
    "detail": "Cascade scheduling request is not valid. Violations: the content was not found for the cascade template stage [cascadeTemplateId:31,634;stageUuid:6467a97d-c0b5-486b-9f94-733297b668de;channelType:WHATSAPP]"
}

There are no channel parameters in the content object that are not in the cascade, and there are no channel parameters that are in the cascade​

Request​

The viberContent and smsContent parameters are passed in the request below, although the cascade with cascadeId = 31634 includes Viber and WhatsApp channels.

curl --location 'http://app.edna.io/api/cascade/schedule' \
--header 'Content-Type: application/json' \
--header 'x-api-key: **********' \
--data '{
    "requestId": "8bcb602f-ce61-4bce-a021-5dc52125a194",
    "cascadeId": 31634,
    "subscriberFilter": {
        "address": "+70000008000",
        "type": "PHONE"
    },
    "content": {
        "viberContent": {
            "contentType": "TEXT",
            "text": "cascade viber  --> whatsapp. No whatsapp content"
        },
        "smsContent": {
            "contentType": "TEXT",
            "text": "cascade viber  --> whatsapp. No whatsapp content"
        }
    }
}'

Response​

{
    "title": "cascade-scheduling-request-not-valid",
    "status": 400,
    "detail": "Cascade scheduling request is not valid. Violations: the content was not found for the cascade template stage [cascadeTemplateId:31,634;stageUuid:6467a97d-c0b5-486b-9f94-733297b668de;channelType:WHATSAPP]; the cascade template stage was not found for the content [cascadeTemplateId:31,634;contentChannelType:SMS]"
}

Errors when Receiving Message Statuses​

Errors during unsuccessful message delivery and receipt of the UNDELIVERED status on the callback for receiving message statuses.

File IconReceiving Message Statuses
ErrorDescription
not-WhatsApp-userThe specified recipient is not registered in WhatsApp.
no-template-matchThe message does not match a valid template.
session-not-started The message is not sent within the 24-hour dialog and does not match a valid template.
daily-rate-limitWhatsApp's daily limit for sending template messages has been exceeded. Only for WhatsApp channel.
too-long-messageThe message length exceeds the allowed limit.
chat-window-closedError opening the dialog box on the WhatsApp side.
media-request-failedFile upload error.
error-subject-unknownThe specified signature is not allowed to the client. All signatures must be activated beforehand.
error-address-formatIncorrect subscriber number format.
duplicatedAttempt to send a duplicate message within 5 minutes.
message-undeliverableThe message could not be delivered to the recipient. Possible reasons:

-The recipient's phone number is not in WhatsApp.

- The recipient has not accepted the new versions of the WhatsApp user agreement and privacy policy.

- The recipient uses an old version of WhatsApp. Use WhatsApp version 2.21.15.15 (Android) or 2.21.170.4 (iOS) and higher.

- Sending authorization messages to recipients with the code +91 (India) is not available.

developers.facebook.com
spam-rate-limit-hitThe message could not be delivered to the recipient because many previous messages were blocked or marked as spam.
marketing-template-undeliverableThe message could not be delivered to the recipient. The delivery limit for marketing messages has been reached for the recipient. Try to send a message later.

developers.facebook.com