--- title: "Send binary SMS message" method: POST path: "/sms/2/binary/advanced" tags: ["channels", "sms", "outbound-sms", "send-message"] --- # Send binary SMS message `POST /sms/2/binary/advanced` ## Request - Base URL: `https://api.infobip.com` (the document declares no server; this is the origin it was published from) - URL: `https://api.infobip.com/sms/2/binary/advanced` - Auth: one of: - OAuth 2 - Client credentials - Token URL: `https://api.infobip.com/auth/1/oauth2/token` - API key in header `Authorization` - API key in header `Authorization` - HTTP basic 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](https://www.infobip.com/docs/api/channels/sms/sms-messaging/logs-and-status-reports/receive-outbound-sms-message-report) instead.\ In light of improved features, this endpoint has been superseded. Please visit [Send SMS message](#channels/sms/send-sms-messages) for the next version. ## Request body - 7b23cc7ec456214e90b61e3d5abd3aaf7422ea4b20f1cdd2d4e9c44fbceaf035SMSAdvancedBinaryRequest - `bulkId` string: 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](#channels/sms/get-outbound-sms-message-delivery-reports) and [message logs](#channels/sms/get-outbound-sms-message-logs). Anything above 100 characters passed in the request will be clipped during processing and returned in response, reports and logs. - `messages` 20085a4036d67f66ebf204560d55d58a7c131c15d42c8ed9442747c488e08630SMSBinaryMessage[], required: An array of message objects of a single message or multiple messages sent under one bulk ID. - `binary` 20085a4036d67f66ebf204560d55d58a7c131c15d42c8ed9442747c488e08630BinaryContent - `dataCoding` integer: Binary content data coding. The default value is (`0`) for GSM7. Example: (`8`) for Unicode data. - `esmClass` integer: “Esm_class” parameter. Indicate special message attributes associated with the SMS. Default value is (`0`). - `hex` string, required: Hexadecimal string. This is the representation of your binary data. Two hex digits represent one byte. They should be separated by the space character (Example: `0f c2 4a bf 34 13 ba`). - `callbackData` string: Additional data that can be used for identifying, managing, or monitoring a message. Data included here will also be automatically included in the message [Delivery Report](#channels/sms/get-outbound-sms-message-delivery-reports). The maximum value is 4000 characters. - `deliveryTimeWindow` 87cf6d665490382407be009353007f071b1d6d4a375e96d31d3bf0b04b7fb3c7DeliveryTimeWindow: Sets specific SMS delivery window outside of which messages won't be delivered. Often, used when there are restrictions on when messages can be sent. - `days` 20085a4036d67f66ebf204560d55d58a7c131c15d42c8ed9442747c488e08630DeliveryDay[], required: Days of the week which are included in the delivery time window. At least one day must be provided. Separate multiple days with a comma. - `from` 20085a4036d67f66ebf204560d55d58a7c131c15d42c8ed9442747c488e08630DeliveryTimeFrom: The exact time of day to start sending messages. Time is expressed in the UTC time zone. If set, use it together with the `to` property with minimum 1 hour difference. - `hour` integer, required: Hour when the time window opens when used in the `from` property or closes when used in the `to` property. - `minute` integer, required: Minute when the time window opens when used in the `from` property or closes when used in the `to` property. - `to` 20085a4036d67f66ebf204560d55d58a7c131c15d42c8ed9442747c488e08630DeliveryTimeTo: The exact time of day to end sending messages. Time is expressed in the UTC time zone. If set, use it together with the `from` property with minimum 1 hour difference. - `hour` integer, required: Hour when the time window opens when used in the `from` property or closes when used in the `to` property. - `minute` integer, required: Minute when the time window opens when used in the `from` property or closes when used in the `to` property. - `destinations` 20085a4036d67f66ebf204560d55d58a7c131c15d42c8ed9442747c488e08630Destination[], required: An array of destination objects for where messages are being sent. A valid destination is required. - `messageId` string: The ID that uniquely identifies the message sent. Anything above 200 characters passed in the request will be clipped during processing and returned in response, reports and logs. - `to` string, required: Message destination address. Addresses must be in international format (Example: `41793026727`). - `flash` boolean: Allows for sending a [flash SMS](https://www.infobip.com/docs/sms/message-types#flash-sms) to automatically appear on recipient devices without interaction. Set to `true` to enable flash SMS, or leave the default value, `false` to send a standard SMS. - `from` string: The sender ID which can be alphanumeric or numeric (e.g., `CompanyName`). Make sure you don't exceed [character limit](https://www.infobip.com/docs/sms/get-started#sender-names). - `intermediateReport` boolean: The [real-time intermediate delivery report](https://www.infobip.com/docs/api#channels/sms/receive-outbound-sms-message-report) containing GSM error codes, messages status, pricing, network and country codes, etc., which will be sent on your callback server. Defaults to `false`. - `notifyContentType` string: Preferred delivery report content type, `application/json` or `application/xml`. - `notifyUrl` string: The URL on your call back server on which the Delivery report will be sent. - `regional` 87cf6d665490382407be009353007f071b1d6d4a375e96d31d3bf0b04b7fb3c7RegionalOptions: Region-specific parameters, often imposed by local laws. Use this, if country or region that you are sending an SMS to requires additional information. - `indiaDlt` 87cf6d665490382407be009353007f071b1d6d4a375e96d31d3bf0b04b7fb3c7IndiaDltOptions: Distributed Ledger Technology (DLT) specific parameters required for sending SMS to phone numbers registered in India. - `contentTemplateId` string: Registered DLT content template ID which matches message you are sending. - `principalEntityId` string, required: Your assigned DLT principal entity ID. - `telemarketerId` string: Your assigned Telemarketer ID. (required for Aggregators) - `turkeyIys` 87cf6d665490382407be009353007f071b1d6d4a375e96d31d3bf0b04b7fb3c7TurkeyIysOptions: IYS regulations specific parameters required for sending promotional SMS to phone numbers registered in Turkey. - `brandCode` integer: Brand code is an ID of the company based on a company VAT number. If not provided in request, default value is used from your Infobip account. - `recipientType` 'BIREYSEL' | 'TACIR', required: Recipient Type must be `TACIR` or `BIREYSEL`. - `southKorea` 87cf6d665490382407be009353007f071b1d6d4a375e96d31d3bf0b04b7fb3c7SouthKoreaOptions: Use case dependent parameters for sending SMS to phone numbers registered in South Korea. - `resellerCode` integer: Reseller identification code: 9-digit registration number in the business registration certificate for South Korea. Resellers should submit this when sending. - `title` string: Set the title or subject of a message. South Korea only. - `sendAt` string, date-time: Date and time when the message is to be sent. Used for [scheduled SMS](https://www.infobip.com/docs/api#channels/sms/get-scheduled-sms-messages). Has the following format: `yyyy-MM-dd'T'HH:mm:ss.SSSZ`, and can only be scheduled for no later than 180 days in advance. - `validityPeriod` integer: The message validity period in minutes. When the period expires, it will not be allowed for the message to be sent. Validity period longer than 48h is not supported (in this case, it will be automatically set to 48h). - `entityId` string: Required for entity use in a send request for outbound traffic. Returned in notification events. For more details, see our [documentation](https://www.infobip.com/docs/cpaas-x/application-and-entity-management). - `applicationId` string: Required for application use in a send request for outbound traffic. Returned in notification events. For more details, see our [documentation](https://www.infobip.com/docs/cpaas-x/application-and-entity-management). - `campaignReferenceId` string: ID that allows you to track, analyze, and show an aggregated overview and the performance of individual campaigns per sending channel. - `sendingSpeedLimit` 87cf6d665490382407be009353007f071b1d6d4a375e96d31d3bf0b04b7fb3c7SendingSpeedLimit: 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. - `amount` integer, required: The number of messages to be sent per timeUnit. By default, the system sends messages as fast as the infrastructure allows. Use this parameter to adapt sending capacity to your needs. The system is only able to work against its maximum capacity for ambitious message batches. - `timeUnit` 'MINUTE' | 'HOUR' | 'DAY': The time unit to define when setting a messaging speed limit. Defaults to `MINUTE`. ## Response `200` successful response - 33e5f9b198702dad16ca1f81c1bb567a11b08d145013a25f78031b56a52d656bSMSResponse - `bulkId` string: 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](#channels/sms/get-outbound-sms-message-delivery-reports) and [message logs](#channels/sms/get-outbound-sms-message-logs). - `messages` 20085a4036d67f66ebf204560d55d58a7c131c15d42c8ed9442747c488e08630SMSResponseDetails[]: An array of message objects of a single message or multiple messages sent under one bulk ID. - `messageId` string: Unique message ID. If not passed, it will be automatically generated and returned in a response. - `status` 20085a4036d67f66ebf204560d55d58a7c131c15d42c8ed9442747c488e08630Status: Indicates the [status](https://www.infobip.com/docs/essentials/response-status-and-error-codes#api-status-codes) of the message and how to recover from an error should there be any. - `groupId` integer: Status group ID. - `groupName` string: Status group name that describes which category the status code belongs to, e.g. PENDING, UNDELIVERABLE, DELIVERED, EXPIRED, REJECTED. - `id` integer: Status ID. - `name` string: [Status name](https://www.infobip.com/docs/essentials/response-status-and-error-codes). - `description` string: Human-readable description of the status. - `action` string: Action that should be taken to recover from the error. - `to` string: The destination address of the message. - `smsCount` integer: This is the total count of SMS submitted in the request. SMS messages have a character limit and messages longer than that limit will be split into multiple SMS and reflected in the total count of SMS submitted. ## Other responses - `400`: Error responses - `401`: Unauthorized - `403`: Forbidden - `500`: Internal Server Error --- [API](https://skmtc.dev/infobip/apis/infobip-openapi-specification-2.md) - [All operations](https://skmtc.dev/infobip/apis/infobip-openapi-specification-2/llms.txt) - [OpenAPI document](https://skmtc.dev/infobip/apis/infobip-openapi-specification-2/revisions/4a6f8044a927?raw)