Skip to main content
POST

Authorizations

Authorization
string
header
default:App
required

This is the most secure authorization type and the one with the most flexibility.

API keys can be generated by calling the dedicated API method. Furthermore, API keys can have a limited scope and cover only some API methods. Lastly, they can be revoked at any time. This range of possibilities makes API keys well suited for separating the API access rights across multiple applications or use cases. Finally, the loss of an API key is easily manageable.

You can manage your API keys from GUI, or programmatically with dedicated API.

API key Authorization header example:

Body

application/json
messages
FailoverMessage · object[]
required

An array of messages being sent.

Minimum array length: 1
bulkId
string

The ID that uniquely identifies the request. Bulk ID will be received only when you send a message to more than one destination address.

Maximum string length: 100

Response

Message accepted for delivery

messages
SingleMessageInfo · object[]

Array of sent message objects, one object per every message.

bulkId
string

The ID that uniquely identifies the request. Bulk ID will be received only when you send a message to more than one destination address.

Example:

"2034072219640523073"