Email API

Send transactional emails and track delivery through the full message lifecycle. Configure sending domains and authorized senders, compose messages with rich content options, and monitor opens, clicks, bounces, and delivery events.

Base URL: https://connect.routee.net

New to the HTTP API? Start with Send your first transactional email. Product context: E-mail.

Before you integrate

Requirement	Description
Active subscription	Transactional Email package on go.routee.net (Email → Pricing → My Plan)
Verified sender	`from` address or domain verified in your account
OAuth application	Connect app with Transactional Email role and scope `transactional_email`

Domain setup: Domain & authorized senders.

Authentication

Create an application on go.routee.net and note Application ID and Application Secret.
Request a token with HTTP Basic auth (-u id:secret):

curl -X POST 'https://auth.routee.net/oauth/token' \
  -u 'APPLICATION_ID:APPLICATION_SECRET' \
  -H 'Content-Type: application/x-www-form-urlencoded' \
  -d 'grant_type=client_credentials&scope=transactional_email'

Pass Authorization: Bearer {access_token} on all endpoints below.

Full walkthrough: Get authenticated using your application credentials.

Send & track

Step	Method	Endpoint	Reference
1. Send	`POST`	`/transactional-email`	Send a transactional email
2. Search logs	`POST`	`/email/tracking`	Search email tracking
3. Batch status	`GET`	`/email/tracking/batch/{trackingId}`	Get email tracking (batch summary)
4. Recipient timeline	`GET`	`/email/tracking/single/{trackingId}/recipients/{messageId}`	Get email tracking (recipient timeline)
5. Single timeline	`GET`	`/email/tracking/single/{trackingId}`	Get email tracking (single message timeline)

HTTP 200 on send means the message was accepted for processing, not delivered to the inbox. Log rows may take 1–2 minutes after send.

For multi-recipient sends, use batch summary then recipient timeline. For single-recipient or legacy rows, use single timeline.

Delivery callbacks (webhooks)

Configure callbacks on POST /transactional-email instead of polling when you want push updates.

Topic	Where
Tutorial	Receive transactional email delivery callbacks — `statusCallback`, `eventCallback`, retry rules
Status & events guide	Email tracking, statuses & callbacks
Request fields	Callback Object Explained, Status Callback Object Explained, DSN Object Explained

Callbacks are HTTP send only — SMTP relay uses the same tracking endpoints for polling.

Domain setup

Method	Endpoint	Reference
`GET`	`/email-senders/domain`	Retrieving a list of domains

Tracking identifiers

Id	Use
trackingId	Batch id from `POST /transactional-email` — batch summary, recipient timeline path, search query `?trackingId=`, and search filter `fieldName: trackingId`
messageId	Per-recipient timeline key from search list or batch `recipients[]`

Multi-recipient sends: one trackingId, many messageId values. Legacy single-recipient rows may use one id for both.

Production behavior

Customer sends on connect.routee.net follow the same path in production as in dev:

OAuth — POST https://auth.routee.net/oauth/token with scope=transactional_email
Send — POST /transactional-email (menshen routes to transactional-email and injects the account principal)
Billing — usage charged against the account's Transactional Email subscription
Delivery — message queued to the email worker; logs on POST /email/tracking within 1–2 minutes

SMTP relay (smtp10.amdtelecom.net) uses the same Connect application credentials; billing runs at SMTP AUTH via the MailerQ plugin. See Transactional Email — SMTP relay.

Migration: Integrators moving from email.routee.net must activate a Transactional Email package on go.routee.net before sending via Connect.

Request & Response Objects

Field-by-field documentation for the send request and response payload: Request & Response Objects.

Retired (not for new integrations)

SendGrid and Mailjet compatibility facades were removed from the product. Use Send a transactional email or Transactional Email — SMTP relay.