curl --request POST \
--url https://api.messaging.phonovation.com/sms/2/binary/advanced \
--header 'Authorization: <api-key>' \
--header 'Content-Type: application/json' \
--data '
{
"bulkId": "BULK-ID-123-xyz",
"messages": [
{
"binary": {
"dataCoding": 0,
"esmClass": 0,
"hex": "54 65 73 74 20 6d 65 73 73 61 67 65 2e"
},
"callbackData": "DLR callback data",
"destinations": [
{
"messageId": "MESSAGE-ID-123-xyz",
"to": "353861234579"
},
{
"to": "353861234582"
}
],
"from": "InfoSMS",
"intermediateReport": true,
"notifyContentType": "application/json",
"notifyUrl": "https://www.example.com/sms/advanced",
"validityPeriod": 720,
"campaignReferenceId": "summersale"
},
{
"binary": {
"dataCoding": 0,
"esmClass": 0,
"hex": "41 20 6C 6F 6E 67 20 74 …20 45 6D 70 69 72 65 2E"
},
"deliveryTimeWindow": {
"days": [
"MONDAY",
"TUESDAY",
"WEDNESDAY",
"THURSDAY",
"FRIDAY",
"SATURDAY",
"SUNDAY"
],
"from": {
"hour": 6,
"minute": 0
},
"to": {
"hour": 15,
"minute": 30
}
},
"destinations": [
{
"to": "353861234578"
}
],
"from": "353861234578",
"sendAt": "2021-08-25T16:00:00.000+0000"
}
]
}
'{
"bulkId": "2034072219640523072",
"messages": [
{
"messageId": "2250be2d4219-3af1-78856-aabe-1362af1edfd2",
"status": {
"description": "Message sent to next instance",
"groupId": 1,
"groupName": "PENDING",
"id": 26,
"name": "PENDING_ACCEPTED"
},
"to": "353861234579"
}
]
}Send binary SMS message
Send single or multiple binary messages to one or more destination address. The API response will not contain the final delivery status, use Delivery Reports instead.
In light of improved features, this endpoint has been superseded. Please visit Send SMS message for the next version.
Required scope: Enable one of: message:send, sms:message:send, sms:manage.
curl --request POST \
--url https://api.messaging.phonovation.com/sms/2/binary/advanced \
--header 'Authorization: <api-key>' \
--header 'Content-Type: application/json' \
--data '
{
"bulkId": "BULK-ID-123-xyz",
"messages": [
{
"binary": {
"dataCoding": 0,
"esmClass": 0,
"hex": "54 65 73 74 20 6d 65 73 73 61 67 65 2e"
},
"callbackData": "DLR callback data",
"destinations": [
{
"messageId": "MESSAGE-ID-123-xyz",
"to": "353861234579"
},
{
"to": "353861234582"
}
],
"from": "InfoSMS",
"intermediateReport": true,
"notifyContentType": "application/json",
"notifyUrl": "https://www.example.com/sms/advanced",
"validityPeriod": 720,
"campaignReferenceId": "summersale"
},
{
"binary": {
"dataCoding": 0,
"esmClass": 0,
"hex": "41 20 6C 6F 6E 67 20 74 …20 45 6D 70 69 72 65 2E"
},
"deliveryTimeWindow": {
"days": [
"MONDAY",
"TUESDAY",
"WEDNESDAY",
"THURSDAY",
"FRIDAY",
"SATURDAY",
"SUNDAY"
],
"from": {
"hour": 6,
"minute": 0
},
"to": {
"hour": 15,
"minute": 30
}
},
"destinations": [
{
"to": "353861234578"
}
],
"from": "353861234578",
"sendAt": "2021-08-25T16:00:00.000+0000"
}
]
}
'{
"bulkId": "2034072219640523072",
"messages": [
{
"messageId": "2250be2d4219-3af1-78856-aabe-1362af1edfd2",
"status": {
"description": "Message sent to next instance",
"groupId": 1,
"groupName": "PENDING",
"id": 26,
"name": "PENDING_ACCEPTED"
},
"to": "353861234579"
}
]
}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
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 to fetch delivery reports and message logs. Anything above 100 characters passed in the request will be clipped during processing and returned in response, reports and logs.
Limits the send speed when sending messages in bulk to deliver messages over a longer period of time. You may wish to use this to allow your systems or agents to handle large amounts of incoming traffic, e.g., if you are expecting recipients to follow through with a call-to-action option from a message you sent. Not setting a send speed limit can overwhelm your resources with incoming traffic.
Show child attributes
Show child attributes
Response
successful response
Unique ID assigned to the request if messaging multiple recipients or sending multiple messages via a single API request. Typically, used to fetch delivery reports and message logs.
An array of message objects of a single message or multiple messages sent under one bulk ID.
Show child attributes
Show child attributes