API delivery receipt error codes

This post was written by on 15th Oct 2009

We have now enabled each of our non-billed SMS routes to support the delivery receipt error codes that were previously only on our premium rate (reverse billed) SMS.

When a message delivery fails and the network returns extra information to us regarding the failure, we can now send this information back to you in a standardised way.

The error code parameter is already defined in section 3.5 of the our API. Please contact us if you want this enabling on your default delivery receipt script. Alternatively, if you set this information when you send a message, you just need to use the ERR_CODE parameter. For instance, if delivery receipts are currently set up to be a GET request using the following parameters:

client_id=#CLIENT_ID#&status=#DELIVERY_STATUS#&msg_id=#MSG_ID#

Then the error code can be also passed by changing this to:

client_id=#CLIENT_ID#&status=#DELIVERY_STATUS#&msg_id=#MSG_ID#&err_code=#ERR_CODE#
The possible error codes are as follows:
Error Number Description Validity
0 No Error
1 Unknown – No details provided by network
2 Message details wrong Permanent
3 Operator Error Permanent
4 Operator Error Temporary
5 Absent Subscriber Permanent
6 Absent Subscriber Temporary
7 Credit Related Temporary
8 Subscriber Bar on Premium Rate content Permanent
9 Phone Related Error Permanent
10 Phone Related Error Temporary
11 Message billed but not be delivered to handset Permanent

Read more posts like this one in API & technical

2 Comments

  1. Gary says:

    yes feel free to link to our blog, we hope you find it useful

Add your comment

What do you think of this blog post? That nagging feeling won’t go away until you let the world know your thoughts.