|MT||Mobile Terminated||A message that has a user (device) as destination. That is, a message that was sent by your company to be delivered to a user (device)|
|Response||Synchronous Movile response||The immediate answer of a request made to our API, where we let you know whether the message was accepted by our platform, or not|
|Callback||Sent status||The first delivery status that we return, where we let you know whether it was possible to deliver the message to the carrier, or not|
|DR ou DLR||Delivery Receipt||The second delivery status we return, where we let you know whether it was possible to deliver the message to the device, or not. The carriers deliver this information to Movile, and we relay it to the client. The time it takes for a DLR to be delivered varies, for example, if the device was turned off at the moment the MT was sent, and the user only turns it on two hours later, this DLR status will be delivered to the client two hours later.
Obs1: This confirmation of delivery on the device will only exist when the message was successfully delivered to the carrier, that is, only if the first status (Callback) was successful.
Obs2: It is very important to make it clear that sadly, some carriers like OI and Sercomtel do not have this functionality. Therefore, they do not give Movile any information of the message being delivered to devices. The deliveries made to these carriers will only have information of delivery to the carrier (Callback).
|MO||Mobile Originated||A message that has your business as destination, that is, messages that were sent by the user (device). MOs are used, for example, during question and answer flows via SMS, when a confirmation is necessary by the user.|
|LA||Short Code||Short number of 5 or 6 digits, used for delivering and receiving SMS messages. They possess anti-fraud and anti-spam rules and carriers only distribute and allow their usage by homologated integrators like Movile|