Get email tracking (recipient timeline)

Returns the ordered event timeline for one recipient inside a batch send.

Path parameters:

  • trackingId — batch id from the send response
  • messageId — per-recipient id from batch summary recipients[].messageId or search list rows

Returns an empty array when the recipient does not belong to the batch. Set include_content=true to include HTML/text body on applicable events.

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

Returns the ordered event timeline for one recipient inside a batch send.

Use this endpoint after Get email tracking (batch summary) when you need the full delivery history (queued, sent, delivered, bounced, opens, clicks) for a single to address.

Authentication

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

Path and query

ParameterLocationDescription
trackingIdpathBatch trackingId from send response (same as batch summary)
messageIdpathPer-recipient worker id from recipients[].messageId 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/recipients/a1b2c3d4-e5f6-7890-abcd-ef1234567890?include_content=false' \
  -H 'Authorization: Bearer YOUR_ACCESS_TOKEN'

Response

JSON array of tracking events (same shape as Get email tracking (single message timeline)).

Returns an empty array when the messageId does not belong to the given batch trackingId.

Troubleshooting fields

Optional fields on timeline rows — same as the single-message timeline:

FieldDescription
results[]SMTP delivery attempts
dsnDelivery Status Notification payload
callbackBodyOpen/click webhook metadata
contentMessage body when include_content=true

IDs

IdRole
trackingId (path)Batch id from send — scopes the request to one HTTP send
messageId (path)Recipient timeline key — unique per to address in the batch

Legacy single-recipient sends may still use Get email tracking (single message timeline) with one id for both search and timeline.

Path Params
string
required

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

string
required

Per-recipient worker message id (timeline key).

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