---
title: "Get an email message"
method: GET
path: "/email_messages/{id}"
tags: ["Email Messages"]
---

# Get an email message

`GET /email_messages/{id}`

## Request

- Base URL: `https://api.telnyx.com/v2`
- URL: `https://api.telnyx.com/v2/email_messages/{id}`
- Auth: HTTP bearer

The legacy `/v2/emails/{id}` GET route is a backward-compatible alias for this operation.

## Path parameters

- `id` string, uuid, required

## Response `200`

Email message details, including plain-text and HTML bodies.

- EmailMessageDetailResponse
  - `data` EmailMessageDetail, required
    - `record_type` 'email_message', required
    - `id` string, uuid, required
    - `status` 'queued' | 'scheduled' | 'cancelled' | 'sandbox' | 'sending' | 'sent' | 'failed' | 'deferred' | 'delivered' | 'bounced' | 'complained' | 'rejected' | 'opened' | 'clicked' | 'unsubscribed', required: Current status of an email message. Lifecycle statuses (queued, scheduled, etc.) are set on creation. Delivery statuses (delivered, bounced, etc.) are updated by delivery event consumers.
    - `from` EmailAddress, required
      - `email` string, required
      - `name` string
    - `to` EmailAddress[], required
      - `email` string, required
      - `name` string
    - `cc` EmailAddress[], required
      - `email` string, required
      - `name` string
    - `bcc` EmailAddress[], required
      - `email` string, required
      - `name` string
    - `reply_to` string, nullable, required
    - `subject` string, required
    - `template_id` string, uuid, nullable, required
    - `template_variables` object, required
    - `tags` string[], required: Customer-supplied tags stored with the message.
    - `metadata` object, required: Customer-supplied metadata stored with the message.
    - `attachments` AttachmentResponse[], required
      - `url` string, uri, nullable, required: Telnyx-hosted public URL for the attachment content.
      - `sha256` string, nullable, required: SHA-256 hex digest of the attachment content.
      - `size_bytes` integer, nullable, required: Attachment size in bytes.
      - `filename` string, required
      - `content_type` string, required
      - `disposition` string, required: MIME disposition (e.g. `attachment` or `inline`). Runtime passes through the stored value without enforcing an enum.
      - `content_id` string, nullable, required: MIME Content-ID for inline references.
    - `events` EmbeddedMessageEvent[], required
      - `type` 'queued' | 'deferred' | 'scheduled' | 'cancelled' | 'sandbox' | 'sending' | 'sent' | 'failed' | 'delivered' | 'bounced' | 'complained' | 'suppressed' | 'rejected' | 'opened' | 'clicked' | 'unsubscribed' | 'daily_limit_exceeded' | 'scan_deferred' | 'quarantined' | 'quarantine_released' | 'quarantine_release_dispatched' | 'quarantine_rejected' | 'quarantine_expired' | 'gw_reject' | 'injection_timeout' | 'expired', required: Bare stored event names returned by message history. In addition to the normal send and delivery lifecycle, polling can expose suppression, scan, and quarantine lifecycle rows. Sharp canonical names gw_reject, injection_timeout, and expired distinguish gateway rejection, ambiguous injection timeout, and MTA expiration. The failed and bounced names remain valid for system/admin failures and hard bounces respectively. Existing stored rows retain their original names.
      - `occurred_at` string, date-time, required
      - `payload` object
    - `created_at` string, date-time, required
    - `scheduled_at` string, date-time: Present when a scheduled_at value was stored. Persists even after the scheduled send has been processed or cancelled.
    - `inline_css` boolean: Present when true in the immediate create response. Not persisted; absent on subsequent GET requests.
    - `sandbox` boolean: Present when sandbox mode was used.
    - `recipient_statuses` object: Per-status recipient counts for the message. Present only for outbound messages with recipient rows. Keys are recipient statuses, values are counts. Example: `{"delivered": 998, "bounced": 2}`.
    - `suppressed` SuppressedRecipient[]: Recipients excluded from delivery by suppression checks, with reasons. On batch items, present when that item had suppressed recipients; all other recipients of the item still receive the message. For single sends this information appears at the top level of the response instead (see EmailMessageResponse.suppressed).
      - `to` string, email, required: Suppressed recipient email address.
      - `reason` string, required: Suppression reason returned by the recipient suppression service.
      - `scope` string, required: Scope at which the suppression applies.
      - `override_allowed` boolean, required: Whether an authorized send may override this suppression.
    - `text_body` string, nullable, required: Plain-text body submitted for the message.
    - `html_body` string, nullable, required: HTML body submitted for the message.

## Other responses

- `401`: Not authorized (10006).
- `404`: Resource not found (10001).

## Changes

- **2026-10-15** `a72569d69430`: 1 info
  - endpoint added

[Operation history](https://skmtc.dev/team-telnyx/apis/telnyx-api/changes/email_messages/:id/get.md)

---

[API](https://skmtc.dev/team-telnyx/apis/telnyx-api.md) - [All operations](https://skmtc.dev/team-telnyx/apis/telnyx-api/llms.txt) - [OpenAPI document](https://skmtc.dev/team-telnyx/apis/telnyx-api/revisions/0f17b8167873?raw)