![]() ![]() Your messages will stay in sent status forever if you are sending messages using the deprecated /SMS/Message REST API Resource, which does not support delivery status updates. #DELIVERY STATUS NOT UPDATED UPDATE#Once a message is older than 72 hours, receiving a further status is unlikely, although we will update the record if we receive one. Please note that US/Canada long code MMS often remain in sent status due to a lack of final delivery status updates from carriers. Typically, a sent status will be replaced by a delivered or undelivered status within seconds or minutes. Twilio has not received updated delivery information for your message. Twilio has received a confirmation from our Super Network partner advising they have accepted the message.Īfter a message has been sent, the following final delivery status options are possible: sent This status is usually only present for a very short time. Twilio is in the process of sending the message. All new messages sent from a specific Twilio phone number are created with a status of queued. Twilio has received your request to create the message. ![]() For details see the Message Scheduling API docs and the Message Scheduling FAQ. The message will remain scheduled until the SendAt time, at which point it will move to the queued status (or failed if there is an issue). (Message Scheduling only) Twilio has received your request to schedule a message for a later time/date. Twilio is determining the optimal 'From' number from your service. (Messaging Services only) Twilio has received your request to create the message from a Messaging Service. When sending outbound messages with the REST API, this is a typical sequence of status values: accepted Every Twilio SMS or MMS message request has a status value which describes the current state of the message. Here are the possible message statuses, and their meanings. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |