Quick guide on how to start the API

With Masiv's SMS Transactional API, any company will be able to connect to our messaging platform through the Software it manages.

With easy and direct integration, all companies will be able to manage their SMS communications in their existing applications.

Important information for sending SMS

Type of message

• Standard: Traditional text message that is saved in the phone's inbox as plain text. This is the most common type of SMS.
• Instant: Also known as Flash SMS. When delivered, it appears directly on the phone's screen, temporarily locking it. It disappears when any key is pressed and is not stored in the inbox. It does not allow user interaction. Important: This type of message is not available in all countries, so it is recommended to validate it before sending.

Message format

• Short: Up to 160 characters, equivalent to 1 message. Special characters are not allowed.
• Long: Up to 1,000 characters, equivalent to a maximum of 7 messages. Every 153 characters is counted as one message. Although it is divided internally, the recipient receives it as a single message. Special characters are not supported. Note: Marking a message as long does not mean that it must exceed 160 characters, but allows you to do so if necessary.
• Rich text: Allows emojis and special characters. Up to 1,000 characters, equivalent to a maximum of 16 messages. In this case, every 63 characters are counted as one message. Like the long format, the recipient receives it as a single message.

Sending restrictions for Colombia (Law 2300 and RNE):

The SMS Transactional API has the functionality to apply the sending restrictions dictated by Law 2300 or Touch Law for Colombia, as well as the validation on the RNE (Law 2300 of Colombia regulates the sending of text messages with advertising and/or billing content to limit the amount of messages sent to end users and also to be sent within the allowed hours: Monday through Friday from 7:00 a.m. to 7:00 p.m., and Saturdays from 8:00 a.m. to 3:00 p.m., excluding Sundays and holidays).

In order for the API to apply the validations on restrictions, it is necessary to enable such features in the account settings, Masiv staff has the ability to adjust the settings to enable the restrictions.

<aside> 💡

Note: Clarification on 2300 compliance and RNE consultation.

The API performs the necessary validations to ensure compliance with Law 2300 and consultation of the National Registry of Exclusions (RNE), as long as the associated restrictions and parameters are active in the account from which the consumption is being made.

</aside>

Postman collection

MasivSmsTransactionalApi.postman_collection.json

Authentication

All SMS Transactional API endpoints require authentication. For this, it is necessary that in each of the requests that are made, an authentication header of the Basic Authentication type corresponding to a valid Masiv user is included.