Email resources overview

Connect endpoint index — send, search tracking, single timeline, and SMTP relay.

Email resources overview

Start here: E-mail — documentation hub.

Transactional Email API v2 on Connect (https://connect.routee.net). All endpoints require Authorization: Bearer {access_token} with OAuth scope transactional_email (or all).

Obtain a token: Get authenticated using your application credentials.


Available resources

MethodPathDescriptionReference
POST/transactional-emailQueue a transactional email (HTTP send)Send a transactional email
POST/email/trackingSearch delivery logs (paginated)Search email tracking
GET/email/tracking/batch/{trackingId}Latest status per recipient (batch send)Get email tracking (batch summary)
GET/email/tracking/single/{trackingId}/recipients/{messageId}Full timeline for one recipientGet email tracking (recipient timeline)
GET/email/tracking/single/{trackingId}Full event timeline (single message / legacy)Get email tracking (single message timeline)

Send — POST /transactional-email

Creates and queues a message. Routed through menshen to the transactional-email service.

ItemDetail
Required body fieldsfrom, to, content
HTTP 200Message accepted for processing — not inbox delivery
Response{ "trackingId": "..." }
CallbacksOptional callback.statusCallback, callback.eventCallback

Billing is applied automatically against your Transactional Email subscription (Email → Pricing → My Plan on go.routee.net).

Common HTTP 400 errors

errorCodeCause
000000Invalid or unverified domain
000001Invalid sender
000002Unverified sender
000003Message size limit exceeded
000004No active subscription
000005Insufficient subscription resources

Setup: Domain & authorized senders


Tracking — POST /email/tracking

Query paramDescription
dateStart, dateEndISO-8601 UTC range
trackingIdOptional — narrow to one message's events
page, sizePagination (default page 0, size 20)

Request body: JSON array of search filters, or [].

Log rows typically appear 1–2 minutes after send.


Batch summary — GET /email/tracking/batch/{trackingId}

Query paramDescription
dateStart, dateEndOptional ISO-8601 UTC range
trackingIdPath — batch id from send response

Response: { "trackingId": "...", "recipients": [ ... ] } — one latest-status row per to address. Each recipients[].messageId is the timeline key.


Recipient timeline — GET /email/tracking/single/{trackingId}/recipients/{messageId}

ParameterDescription
trackingIdPath — batch id from send
messageIdPath — per-recipient id from batch summary or search list
include_contentDefault false. Set true to include HTML/text body

Returns a JSON array of events. Empty array when messageId is not part of the batch.


Single timeline — GET /email/tracking/single/{trackingId}

Returns a JSON array of ordered events (not a page).

Query paramDescription
include_contentDefault false. Set true to include HTML/text body on events

SMTP relay (non-HTTP)

Customer MailerQ relay — not a Connect REST path:

SettingValue
Hostsmtp10.amdtelecom.net
AuthApplication Id / Application Secret
Port 25STARTTLS
Port 587Implicit TLS

Guide: Transactional Email — SMTP relay

SMTP sends appear in the same tracking endpoints above.


Related products

ProductDocs
Email ValidatorEmail Validator — validate addresses before send (separate API)
Legacy Email v1Deprecated — promotional campaigns on email.routee.net

What's next