Send SMS Messages. For FREE!

Our API makes it easy for developers to send and receive ad-supported SMS messages from any website.

Send Ad-free Messages

Want to use all 160 chars. of each message? Sign up for a monthly ad-free plan.
From $9.95/month.

Visit our Google Group
Discuss with other developers, get support and leave us feedback.

Dealing with Errors

Table of Contents

How Responses Work

Zeep Mobile responds to requests with HTTP status codes, here are a couple of examples:

Response to Successful Request

If a request is successful, the response will look like this: 

HTTP/1.1 200 OK
Date: Thu, 11 Mar 2010 07:00:54 GMT
...
Content-Length: 0

You can see that the response status code is 200. This means that the request has succeeded.

Response to Unsuccessful Request

In the case of an error, a code between 400 and 599 is used. Also, a human-readable message will be included in the response content.

Here is an example of an error reponse code 401, a failed authentication:

HTTP/1.1 401 Unauthorized
Date: Thu, 11 Mar 2010 07:00:54 GMT
...
Content-Type: text/plain
Content-Length: 158
The HMAC+SHA1 signature of your Authorization header was incorrect. Please see http://www.zeepmobile.com/developers/documentation/messaging/2008-07-14/authentication for more details.

Complete Response Listing

There are two classes of error status codes:

The 4xx class of status code is intended for cases in which the client seems to have erred. A request that generates a status code in this range should not be re-attempted.

The 5xx class of status code is used to indicate cases in which the server is aware that it has erred or is incapable of performing the request. Any request that generates this response is logged, and we will deal with the issue as soon as possible. These requests may be re-attempted, but keep in mind the time-sensitivity of the request.

HTTP Code Name What's it mean?
200 OK All is good in the hood.
400 InvalidTimeSignature Message time differs to much from server clock or Date header was not supplied.
400 InvalidArguments Some arguments were missing or invalid.
400 MessageTooLong The message you attempted to send was too many characters for the given method. See the specific method documentation for limitations.
400 InvalidSubscription The subscrtiption specified is not active or is blocking access from your application.
403 InvalidAuthorization The Authorization header was either not supplied or was not the correct format. See the Authentication documentation for more details.
403 SignatureDoesNotMatch The supplied HMAC+SHA1 signature was not valid for the parameter content or Secret Key. See the Authentication documentation for more details.
403 InvalidAPIKey The API Key was either not supplied, or has not been registered as a Zeep Mobile Application.
404 InvalidEndpoint The URL used for the method endpoint is invalid. Make sure you are specifying a valid release date.
405 MethodNotAllowed The HTTP method used is not allowed.
500 InternalServerError An error has occured within the Zeep API. These errors are always logged and we are alerted. We will do our best to fix the problem ASAP.
555 UnexpectedError You got me, this should never happen. If you see a 555 error, please email the contained message to support@zeepmobile.com.