Get email tracking (batch summary)

Returns the latest status per recipient for one HTTP send batch — use the trackingId from Send a transactional email.

Each item in recipients[] includes the per-recipient messageId (timeline key). For the full event history of one recipient, call Get email tracking (recipient timeline).

Optional dateStart / dateEnd (ISO-8601, UTC) bound the search window when resolving recipients.

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

Returns the latest delivery status per recipient for one HTTP send batch.

Use the trackingId from Send a transactional email. For multi-recipient sends, this is the batch id — not the per-recipient timeline key.

Authentication

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

Path and query

ParameterLocationDescription
trackingIdpathBatch trackingId from send response
dateStartqueryOptional ISO-8601 UTC start of range
dateEndqueryOptional ISO-8601 UTC end of range

Example — cURL

curl -X GET 'https://connect.routee.net/email/tracking/batch/51b1738c-5fc5-4aa2-85a4-3b063c486cd7?dateStart=2026-07-01T00:00:00Z&dateEnd=2026-07-10T23:59:59Z' \
  -H 'Authorization: Bearer YOUR_ACCESS_TOKEN'

Response

FieldDescription
trackingIdEcho of the batch id
recipients[]One summary row per recipient (latest event)

Each recipients[] item includes:

FieldDescription
messageIdPer-recipient id — pass to Get email tracking (recipient timeline)
recipient, from, subjectEnvelope summary
status, deliveryStatus, eventLatest human-readable and MTA status
channelAPI, SMTP, or MARKETING
dateLatest event timestamp (UTC)
openedCount, clickCountEngagement counters

Next step

For the full queued → sent → delivered timeline of one recipient:

curl -X GET 'https://connect.routee.net/email/tracking/single/BATCH_TRACKING_ID/recipients/RECIPIENT_MESSAGE_ID' \
  -H 'Authorization: Bearer YOUR_ACCESS_TOKEN'

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
date-time

Start of date range (ISO-8601).

date-time

End of date range (ISO-8601).

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