Errors

The EZ Texting Developers' API uses standard HTTP response codes for responses. These HTTP codes indicate whether or not an API operation was successful.

Status Codes in the 200s range are the desired response codes.

Codes in the 400s range detail all of the errors an EZ Texting Developer could encounter while using the API. Bad Request, Rate Limit Reached, and Unauthorized are some of the responses in the 400s block.

Codes in the 500s range are error responses from the EZ Texting system. If an error occurred anywhere in the execution of a resource, and this error was not due to user input, a 500 response will be returned with a corresponding JSON error body. That body will contain a message detailing what went wrong.

The JSON error response body

{
    "status": 400,
    "title": "Malformed Request",
    "detail": "The request you made was malformed",
    "errors": [
        {
            "title": "Sorting Failure",
            "message": "The sort direction query string is required but was missing"
        }      
    ]
}

HTTP Response Codes

Response Code

Meaning

200

OK - Everything went as planned.

201

CREATED - The request has been fulfilled and has resulted in one or more new resources being created.

204

NO CONTENT - Request fulfilled, but no body.

400

BAD REQUEST - The request contained invalid data.

401

UNAUTHORIZED - Authorization header is missing, invalid or expired.

403

FORBIDDEN - Insufficient permissions.

404

NOT FOUND - The resource requested does not exist.

415

UNSUPPORTED MEDIA TYPE - The request has a media type which the resource does not support.

429

TOO MANY REQUESTS - Too many requests were sent within a certain time frame (see Rate Limits).

500

INTERNAL ERROR - We had an error! Sorry about that.


What’s Next