Using the API

The HTTP API allows you to send messages to us using JSON over HTTP. You can either talk to the API using your current HTTP library or you can use one of the pre-built libraries.

Full API documentation

This API does not support managing all the functions of Postal. There are plans to introduce a new v2 API which will have more functionality and significantly better documentation. We do not have an ETA for this. Additionally, we will not be accepting any pull requests to extend the current API to have any further functionality than it currently does.

General API Instructions

  • You should send POST requests to the URLs shown below.
  • Parameters should be encoded in the body of the request and application/json should be set as the Content-Type header.
  • The response will always be provided as JSON. The status of a request can be determined from the status attribute in the payload you receive. It will be success or error. Further details can be found in the data attribute.

An example response body is shown below:


To authenticate to the API you'll need to create an API credential for your mail server through the web interface. This is a random string which is unique to your server.

To authenticate a request to the API, you need to pass this key in the X-Server-API-Key HTTP header.

Sending a message

There are two ways to send a message - you can either provide each attribute needed for the e-mail individually or you can craft your own RFC 2822 message and send this instead.

Full details about these two methods can be found in our API documentation:

For both these methods, the API will return the same information as the result. It will contain the message_id of the message that was sent plus a messages hash with the IDs of the messages that were sent by the server to each recipient.

    "":{"id":37171, "token":"a4udnay1"},
    "":{"id":37172, "token":"bsfhjsdfs"}