Get email tracking (single message timeline)

Returns the ordered event timeline for one message — queued, sent, delivered, bounced, opened, clicked.

Each event includes human-readable status and event fields. Optional results, dsn, and callbackBody are troubleshooting fields (SMTP/MTA detail) — not required for normal monitoring. The portal shows them under collapsed Technical details; failed events may surface short delivery descriptions automatically.

Pass the trackingId from Send a transactional email or from search list rows (Tracking ID column / trackingId field).

Set include_content=true to include HTML/text body on timeline events (list/search omit body by default).

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…

Returns the ordered event timeline for one email message — each row is a delivery or engagement event with optional SMTP diagnostics.

For multi-recipient HTTP sends, prefer Get email tracking (batch summary) and Get email tracking (recipient timeline). This endpoint remains for single-recipient sends and legacy integrations where one id serves both search and timeline.

Authentication

Authorization: Bearer {access_token} with scope transactional_email or all. No Principal header.

Path and query

ParameterLocationDescription
trackingIdpathTracking ID from Send a transactional email response or search list rows
include_contentqueryDefault false. Set true to include HTML/text body on events

Example — cURL

curl -X GET 'https://connect.routee.net/email/tracking/single/51b1738c-5fc5-4aa2-85a4-3b063c486cd7?include_content=false' \
  -H 'Authorization: Bearer YOUR_ACCESS_TOKEN'

Response

JSON array of tracking events (not a page). Typical progression:

event / deliveryStatusMeaning
QUEUEDAccepted by Routee mail pipeline
SENT / DELIVEREDHanded off or confirmed by recipient MTA
BOUNCED / FAILEDPermanent or temporary failure
Open/click eventsPresent when callback.eventCallback was configured on send

Extra fields on timeline rows

Most customers only need the ordered timeline (status, event, date). The fields below are for troubleshooting — shown under Technical details in the portal (collapsed by default), or returned directly in the API.

FieldDescription
resultsSMTP delivery attempts (status, description, DSN flag) — portal shows description automatically on failed events
dsnDelivery Status Notification payload when available
callbackBodyMetadata from open/click callbacks (IP, device, etc.)
contentMessage body when include_content=true

IDs

IdWhere it appearsCustomer use
trackingIdSend response; search list; ?trackingId= on searchPrimary batch id — store after send
messageIdSearch list rows; batch recipients[]Timeline key per to address
Legacy single idSMTP-only or older rowsSame value for both fields — use this endpoint

See Email API for the identifier glossary.

Path Params
string
required

Primary customer tracking id from send response or search trackingId field. Internal messageId also accepted when values differ.

Query Params
boolean
Defaults to false

When true, include message body on applicable events.

Responses

401

Missing or invalid Bearer token

403

Insufficient role or OAuth scope (transactional_email required)

404

Message not found for this account

Language
Credentials
Bearer
JWT
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json