Creates and sends or schedules an email or SMS message. IMPORTANT for email: the content field on this endpoint is the source of truth — exactly that HTML (after server-side macro and link processing) is what subscribers receive. template_id is stored as metadata only; this endpoint does NOT re-render template + resource → HTML. You must build the final HTML on the client first. Typical email workflow: (1) Pick a content type, which determines message_type.name: Article → email-article, Lift Letter → email-promo (when promoted_publication_id is set) or email-renewal (when sending to a renewal cohort), Free Style → email-free-style. (2) Assemble content. For Article / Lift Letter, call GET /messages/contents/{resource_id} (retrieveMessageContent) with template_id, publication_id, message_type_id, plus promoted_publication_id / renewal_type as relevant — use the returned content, subject, and preview_line directly. For Free Style, fetch the template via GET /templates/{template_id} (retrieveTemplate), strip the {$sys_email.content} (or {$sys_email_content}) placeholder, write the body in its place, and use that as content. (3) POST here with the assembled content, plus template_id, subject, sender_id, reply_id, and either included_segment_ids (live) or emails (test). For SMS, provide messaging_service_id, content, and either included_segment_ids (live) or numbers (test). Use splits for A/B testing — each variant carries its own content, template_id, subject, sender_id, reply_id, and amount.
| Time | Status | User Agent | |
|---|---|---|---|
Retrieving recent requests… | |||
