post https://your-callback-url.com/sms_verify_dlr_endpoint
WARNING
Telesign introduced a new version of our SMS Verify API. The previous version was deprecated on 3/30/23 GMT. In the new version, some features (the 229, 230, and 233 statuses and the Verify Plus packages) are returned asynchronously in the Delivery Report. Please see the details in this Changelog post to ensure that your integration is accurate for the version of the API that you are using or it may break.
This is a web service created by you, to receive delivery reports (DLRs) from the Telesign SMS Verify API. You can receive callbacks, including DLRs, from multiple Telesign services at the same endpoint.
Status codes
| Status code | Associated text string | Description |
|---|---|---|
| 200 | Delivered to handset | The SMS was delivered to the end user's phone. (Final) |
| 203 | Delivered to gateway | The SMS was delivered to the gateway. If the gateway responds with further information (including successful delivery to handset or delivery failure), the status is updated. (Intermediate) |
| 207 | Error delivering SMS to handset (reason unknown) | The SMS could not be delivered to the end user's handset for an unknown reason. (Final) |
| 210 | Temporary phone error | The SMS could not be delivered to the handset due to a temporary error with the phone. Examples - phone is turned off, not enough memory to store the message. (Final) |
| 211 | Permanent phone error | The SMS could not be delivered to the handset due to a permanent error with the phone. For example, the phone is incompatible with SMS, or illegally registered on the network. This can happen when a phone number is blacklisted, or is incorrectly provisioned. (Final) |
| 220 | Gateway/network cannot route message | The network cannot route the message to the handset. (Final) |
| 221 | Message expired before delivery | The message was queued by the mobile provider and timed out before it could be delivered to the handset. (Final) |
| 222 | SMS not supported | SMS is not supported by this phone, carrier, plan, or user. |
| 229 | Message blocked by your request | Telesign blocked the SMS before it was sent. This is due to your prior submitted request to blocklist this phone number. Not returned here for customers pinned to the old version of SMS Verify. |
| 230 | Message blocked by Telesign | Telesign blocks a message if it is being sent to a phone number that is on a global blocklist. Not returned here for customers pinned to the old version of the SMS Verify API. |
| 231 | Invalid/unsupported | The content of the message is not supported. |
| 233 | Message blocked due to high risk score. | It was determined that the risk recommendation for the destination number is higher than the configured maximum risk recommendation. For that reason Telesign did not send the SMS. Not returned here for customers pinned to the old version of the SMS Verify API. |
| 237 | Message blocked in requested country | You requested that messages in a specific country be blocked, and the message was being sent to this country. |
| 250 | Final status unknown | The final status of the SMS cannot be determined. |
| 251 | Message successfully sent out for delivery, however final confirmation of delivery to handset was not received. | Telesign successfully delivered the message through our gateway and it passed downstream. However, Telesign did not receive a delivery receipt within 12 hours of transmission. We cannot confirm delivery to the handset. The end user most likely did not receive the message. |
| 292 | Queued by gateway | The SMS gateway has queued the message. |
| 295 | Status delayed | The status of the SMS is temporarily unavailable. |
| 500 | Transaction not attempted. | No SMS request was attempted. |
| 501 | Not authorized | No permissions for this resource, or authorization failed. |
| 502 | Campaign error | This error can be generated if there is a problem with the short code used. |
| 503 | System Unavailable, Please try again later. | Internal system error |
| 504 | Carrier rejected - permanent error | This error is generated if there is an error on the carrier or operator side that is permanent and the message should not be retried. |
| 505 | Error on gateway - temporary error | This error is generated if there is an error on Telesign's partner side that is considered temporary and the message can be retried. |
| 506 | Error on gateway - permanent error | This error is generated if there is an error on Telesign's partner side that is considered permanent and the message should not be retried. |
| 507 | Invalid destination address | There is a problem with the destination address used. Either the format is not valid, or the number is not associated with any carrier, or if MSC is used it does not know about this MSISDN. |
| 508 | Invalid source address | The message requires a source address. Verify that one is provided and correct. |
| 509 | Parameters problem | One or more parameters used in the request is not supported. |
| 510 | Message blocked by subscriber action or request | The end user has blocked receiving SMS with their carrier plan or by request or from the particular short code used. |
| 511 | Subscriber low on credit | The end user exceeded their spending limits and cannot receive SMS. |
| 512 | Roaming error | End user cannot receive SMS because their device that receives the messages is roaming. |
| 513 | Mobile number portability error | SMS failed because ported combinations are unreachable. |
| 514 | Subscriber absent | The operator/carrier is temporarily unable to reach the end user. |
| 515 | Suspected spam | This message is considered to be spam by carrier or operator. |
| 517 | Selected DLT details for India not supported | The DLT template ID or entity ID in the request cannot be found by the end operator. |
| 518 | Message blocked due to high risk SIM swap indicator. | The service determined that the SIM swap risk indicator for the destination number is higher than the maximum value configured for your account. For that reason Telesign did not send the SMS. |
| 519 | Message not sent - requested SIM swap check could not be performed. | The service could not perform the SIM swap check. This is because either the number is out of SIM swap coverage or information about the potential SIM swap event is missing. |
| 520 | Content sent is not allowed | The content in this message is not permitted by the carrier. |
| 521 | Requested Sender ID is not allowed for destination | The Sender ID included in this request cannot be used to send messages to this destination phone number. The Sender ID may either be blocklisted for this country or needs to be added to a whitelist for this country. |
| 599 | Status not available | The system is unable to provide status at this time. |