Use Trigger API on SE2025

This page is dedicated to universes that are on SE2025, still using Trigger API, and have not yet completed the necessary developments to migrate to the Messaging API. You must eventually complete the required developments to migrate to the Messaging API. This workaround is only intended to provide a short-term solution while your Messaging API set-up is finalized.

❗️

This is a TEMPORARY workaround and is not a permanent solution.

Why migrating to the Messaging API is important

• The Messaging API is a more modern, scalable solution, both for Splio and for our clients.
  • It is GDPR-compliant and aligns with market standards.
• The Trigger API is deprecated for SE2025 and will be sunset; the Messaging API will fully replace it.

What happens to designs when a universe is migrated to SE2025

• When a universe is migrated to SE2025, the associated designs are also migrated to be available in the new Designer (supporting Liquid syntax, etc.).
• Designs previously used with the Trigger API are migrated and assigned new IDs.
• When a user operates via the Messaging API, these migrated designs are accessible and editable through the new Designer without any issues.
• However, if the universe has not yet migrated to the Messaging API, designs with new IDs can technically be updated in the new Designer, but these updates are not linked to the Trigger API usage.

👉Therefore, users CANNOT rely on the new Designer to edit designs for active Trigger API workflows.

How to update a design used in the Trigger API on SE2025

1. Access the old Designer using the following URL 👉 https://sp-ring.com/{{universe}}/designer/emails
2. Select the design associated with the Trigger API that you wish to update
3. Make updates using the old syntax (not Liquid)
4. Save your changes

Limitations of this workaround

• Limited design access
  • Access is only possible through a hidden, non-standard URL
  • Changes must be made using the old syntax, which can be confusing for users getting familiar with Liquid
  • No auto-save functionality
• Limited reporting
  • The Campaign Performance Dashboard is only available for campaigns sent via Messaging API
  • Reports for the Trigger API are still available in Campaigns > Automations > Trigger API tab