Update an email message
Email messages
Update an email message
Update fields on a Loops email message, including subject, from address, preview text, and LMX content revisions for campaign or transactional drafts.
POST
Update an email message
Request
The campaign or transactional email that owns this email message must be in
Draft status.Path parameters
The ID of the email message.
Body
The
contentRevisionId you last fetched, or the emailMessageContentRevisionId you received when creating the campaign. Used for optimistic concurrency.Email subject line.
Email preview text.
Sender display name.
The sender username (without
@ or domain). The team’s sending domain is
appended automatically.Reply-to email. Must be empty or a valid email address.
CC email address. Requires the team to have CC/BCC enabled.
BCC email address. Requires the team to have CC/BCC enabled.
Language code for the email. Requires translation to be enabled for the team.
The rendering format of the email. One of
styled or plain.The email body serialized as LMX. Styles must be embedded in the LMX
<Style /> tag. The LMX payload must not exceed 100KB.Fallback values for contact properties, keyed by property name. Per-key
merge: a string value sets the fallback, a
null value deletes it, and keys
omitted from the map are left unchanged.Fallback values for event properties, keyed by property name. Per-key merge:
a string value sets the fallback, a
null value deletes it, and keys
omitted from the map are left unchanged.Fallback values for data variables, keyed by variable name. Per-key merge:
a string value sets the fallback, a
null value deletes it, and keys
omitted from the map are left unchanged.Response
Success
Present only when the message belongs to a campaign.
Present only when the message belongs to a transactional email.
Only present when set.
Only present when set.
Only present when set.
One of
styled or plain.The current content revision ID. Use this value as
expectedRevisionId on
your next update request.Contact property fallbacks. Only present when set.
Event property fallbacks. Only present when set.
Data variable fallbacks. Only present when set.
Non-fatal issues raised while compiling the submitted LMX. Only present on update responses when warnings were produced.
Error
If the request body is invalid, a400 Bad Request is returned.
A 404 Not Found is returned if the email message does not exist.
A 409 Conflict is returned when the campaign is not in draft status, when
contentRevisionId is stale, when content cannot be parsed, or when the email message uses MJML format.
A 413 Payload Too Large is returned when the LMX payload exceeds the 100KB limit.
A 422 Unprocessable Entity is returned when LMX compilation fails.
If the API key is invalid (or content API is not enabled for your team), a
401 Unauthorized is returned.
Last modified on June 30, 2026

