Send a transactional email. You can either use a saved template (by slug) or send custom content directly.
Request Body Option 1: Send via template Template slug (use this OR subject+body)
Option 2: Send direct content Email subject (required if no slug)
Email HTML body (required if no slug)
Common fields Template variables for personalization
Example: Send via template curl -X POST "https://api.sequenzy.com/api/v1/transactional/send" \ -H "Authorization: Bearer YOUR_API_KEY" \ -H "Content-Type: application/json" \ -d '{ "to": "[email protected] ", "slug": "welcome", "variables": { "NAME": "John", "LOGIN_URL": "https://app.sequenzy.com/login" } }' Example: Send direct content curl -X POST "https://api.sequenzy.com/api/v1/transactional/send" \ -H "Authorization: Bearer YOUR_API_KEY" \ -H "Content-Type: application/json" \ -d '{ "to": "[email protected] ", "subject": "Your order is confirmed", "body": "<h1>Thank you, {{NAME}}!</h1><p>Order #{{ORDER_ID}} confirmed.</p>", "variables": { "NAME": "John", "ORDER_ID": "12345" } }' Responses 200 Template
200 Direct
400 Missing fields
400 Disabled
400 Missing variables
400 No sender
404
401
500
{ "success" : true , "jobId" : "job_xyz789" , "to" : "[email protected] " , "transactional" : { "id" : "txn_abc123" , "slug" : "welcome" , "name" : "Welcome Email" } }
Emails are queued for background processing. The jobId can be used to track delivery status. System variables like NAME, FIRST_NAME, LAST_NAME, and EMAIL are automatically populated from subscriber data if available.
