---
title: "Get an email message"
method: GET
path: "/v1/email-messages/{emailMessageId}"
tags: ["Email messages"]
---

# Get an email message

`GET /v1/email-messages/{emailMessageId}`

Retrieve an email message, including its compiled LMX content.

## Response `200`

Successful.

- EmailMessageResponse
  - `id` string, required — The ID of the email message.
  - `campaignId` string — The campaign this email message belongs to. Present only when the message belongs to a campaign (mutually exclusive with `transactionalId`).
  - `transactionalId` string — The transactional email this email message belongs to. Present only when the message belongs to a transactional email (mutually exclusive with `campaignId`).
  - `subject` string, required — The email subject.
  - `previewText` string, required — The email preview text.
  - `fromName` string, required — The email sender name.
  - `fromEmail` string, required — The email sender email address, without the team's sending domain.
  - `replyToEmail` string, required — The email reply-to address.
  - `ccEmail` string — The email CC address. Only present when set.
  - `bccEmail` string — The email BCC address. Only present when set.
  - `languageCode` string — ISO 639-1 language code for the email, e.g. `en` or `fr`. Only present when set.
  - `emailFormat` 'styled' | 'plain', required — The rendering format of the email.
  - `lmx` string, required — The email body serialized as LMX.
  - `contentRevisionId` string, nullable, required — The current content revision. Pass this as `expectedRevisionId` on your next update.
  - `updatedAt` string, date-time, required
  - `contactPropertiesFallbacks` object — Fallback values for contact properties. Only present when set.
  - `eventPropertiesFallbacks` object — Fallback values for event properties. Only present when set.
  - `dataVariablesFallbacks` object — Fallback values for data variables. Only present when set.
  - `warnings` object[] — Non-fatal issues raised while compiling the submitted LMX. Only present on update responses when warnings were produced.
    - `rule` string, required
    - `severity` 'warning', required
    - `message` string, required
    - `path` string

## Other responses

- `400` — Invalid `emailMessageId` or no sending domain configured.
- `401` — Invalid API key or content API not enabled for this team.
- `404` — Email message not found.
- `405` — Wrong HTTP request method.
- `409` — Email message uses MJML format or content cannot be parsed.

---

[API](https://skmtc.net/loops/apis/loops-openapi-spec.md) · [All operations](https://skmtc.net/loops/apis/loops-openapi-spec/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/loops/loops-openapi-spec/versions/96c4b50b8b95/schema)