In the last Marketing Cloud release there is the new transactional messaging API option (https://developer.salesforce.com/docs/atlas.en-us.mc-apis.meta/mc-apis/transactional-messaging-api.htm).

Before we want to enable this option we wondered what this new API call is doing exactly other then a standard normal API call. Why should we use this new API call instead of the standard (server to server) API integration? Is there someone allready use this new option?

Regards, Martijn

2 Answers 2


The advantage is that you can create your definition on the API using REST, as opposed to only using SOAP... I think the data model is a bit cleaner, and the transactional SMS api is also much more similar to e-mail, which would be very helpful to developers.

Unfortunately, there is a lot of missing features as it is a very new API... We couldn't find a way to generate reports, or manage definitions through the UI.

We gave up on using it in production as of now, and we are sticking with good old "Triggered Send".


The Transactional Messaging API brings a lot of benefits:

  • better send performance compared to the older triggered sends
  • consumes only 1 super message rather than 4 for high priority sends while also being faster
  • you have the possibility to either check the results of the send via an API request or having them pushed to an endpoint of yours using the Event Notification Service
  • configuring sends and updating emails is now easier for marketers as the Transactional Messaging API definitions can now be configured using Journey Builder's new Tranactional Send journey type

Further resources:

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .