Messaging API Changes in Splio: What to Expect (2025 Update)

Changes to expect with the messaging API

We recently updated our API to improve the management of your transactional and marketing communications. Two options are now available, both compliant with industry standards.

Option 1: Contacts are already present in Splio

All contact and ticket information is available to personalize messages.
Impact on customization : it is possible via Splio customization fields.
-

Option 2: Contacts are not present in Splio

All contact and ticket information for customizing designs must be sent through the new API.
Impact on Personalization : This is not possible via Splio personalization fields. The data must be included in the API request.

Impacts to be expected compared to the old API

SMTP Relay : No changes to be made, everything will work as before.
Trigger API : This API is deprecated. It's necessary to set up new feeds to the new messaging API with all the necessary information to personalize the message for each contact. This trigger API will remain accessible even after you upgrade to Splio Edition 2025. However, you'll need to make your design changes through the older version, if necessary.

Impact on the use of Message Builder

Regardless of the option (Option 1 or Option 2), you can use the Message Builder.

However, the personalization fields will need to be called differently depending on whether the data is already present in Splio or dynamically passed through the API.