curl --request POST \
--url https://api.messaging.phonovation.com/sms/3/messages \
--header 'Authorization: <api-key>' \
--header 'Content-Type: application/json' \
--data '
{
"messages": [
{
"sender": "InfoSMS",
"destinations": [
{
"to": "353861234579"
}
],
"content": {
"text": "This is a sample message"
}
}
]
}
'{
"bulkId": "2034072219640523072",
"messages": [
{
"messageId": "2250be2d4219-3af1-78856-aabe-1362af1edfd2",
"status": {
"groupId": 1,
"groupName": "PENDING",
"id": 26,
"name": "PENDING_ACCEPTED",
"description": "Message sent to next instance"
},
"destination": "353861234579",
"details": {
"messageCount": 1
}
}
]
}Send SMS message
With this API method, you can do anything from sending a basic message to one person, all the way to sending customized messages to thousands of recipients in one go. It comes with a range of useful features like transliteration, scheduling, and tracking in a unified way.
If utilizing Message Delivery Reports webhook, please consult the documentation provided at Receive outbound SMS message reports.
This endpoint is the successor of Send SMS message and Send binary SMS message.
Required scope: Enable one of: message:send, sms:message:send, sms:manage.
curl --request POST \
--url https://api.messaging.phonovation.com/sms/3/messages \
--header 'Authorization: <api-key>' \
--header 'Content-Type: application/json' \
--data '
{
"messages": [
{
"sender": "InfoSMS",
"destinations": [
{
"to": "353861234579"
}
],
"content": {
"text": "This is a sample message"
}
}
]
}
'{
"bulkId": "2034072219640523072",
"messages": [
{
"messageId": "2250be2d4219-3af1-78856-aabe-1362af1edfd2",
"status": {
"groupId": 1,
"groupName": "PENDING",
"id": 26,
"name": "PENDING_ACCEPTED",
"description": "Message sent to next instance"
},
"destination": "353861234579",
"details": {
"messageCount": 1
}
}
]
}Authorizations
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:
Authorization: App 003026bbc133714df1834b8638bb496e-8f4b3d9a-e931-478d-a994-28a725159ab9
Body
Response
OK
An array of message objects of a single message or multiple messages sent under one bulk ID.
1Show child attributes
Show child attributes
Unique ID assigned to the request if messaging multiple recipients or sending multiple messages via a single API request. If not provided, it will be auto-generated and returned in the API response. Typically used for fetching delivery reports and message logs.