How is a transactional message accessed in the SOAP API?

• A. Available via the TriggeredSend object using the Create method
• B. Route for sending: /messageDefinitionSends
• C. AMPScript for landing pages
• D. Transactional messages are not supported in SOAP

Answer: (A)

Transactional messages in the SOAP API are accessed through the TriggeredSend mechanism. You define a TriggeredSendDefinition that holds the content and sending settings for the transactional message, and to actually send, you call Create on the TriggeredSend object, supplying the CustomerKey of that definition plus the recipient’s SubscriberKey and any personalization attributes. This triggers a one-off, event-driven send using the specified definition. The other options aren’t the SOAP path: REST routes or AMPScript usage aren’t how you initiate a transactional message via SOAP, and it's incorrect to say that transactional messages aren’t supported in SOAP since the supported approach is through TriggeredSend and Create.