service address /api/MessageStatus
verb POST
body application/json
If you get a final status like -200 when you send the MT message the message will not then be avaliable available for query. Only message send with return status 11 are avaiable available for query
Also your account needs to be setup for allowing MO queries. Currently this query can only be used on a single thread. Using multiple threads will most likely return the same result for multiple queries and unnecessarily add load to the system.
When implementing the Querring process you will need to have us approve you application logic. This is so we can confirm you will not over query our system.
Normal Implementation plan;
- use the query to receive non polled messages - the frequency you call this method will determine on your message send rate and behaviour
- Messages will receive a final status not later than 49 hours after it is sent.
- Use the query by document Id only to check for Status if you have not otherwise got a final status after this 49 hour period.
Query Plan
| step | Query |
|---|---|
| 1 | query for unpolled statuses every 2 mins if you are sending messages - if not query every 15 mins |
| 2 | if you receive 50 statuses in one request immediately requery |
| 3 | if after 8 days after sending a message if you do not have a final status query by messageId to get a final status. |
...