How does the Transactional Messaging API differ from triggered sends, and what are the batch size limits?
Suggested answer
Triggered Sends use the legacy SOAP/REST triggered send definition and are associated with a triggered send DE; they have limited throughput and configuration flexibility.
Transactional Messaging API (TM API) is the modern replacement: POST /messaging/v1/email/messages/{messageKey}. Key differences:
— TM API has higher throughput (up to 2,500 emails/minute per MID on dedicated IPs).
— Supports synchronous send status response in near real time.
— Batch endpoint: POST /messaging/v1/email/messages/ accepts up to 50 recipients per batch call.
— Supports attributes and content.customerKey overrides per message.
— Requires a Transaction Definition Key created in Email Studio under Triggered Sends > Transactional Sends.
Practice content for interview preparation; not an official vendor answer. Verify details against current product documentation.
Community comments (0)
No comments yet.
Sign in or create a free account to add a comment. Comments are moderated before they appear.