Introduction

Routee Transactional Email is a REST API for sending one-to-one email from your applications — password resets, order confirmations, account alerts, and other system-triggered messages.

All requests use JSON over HTTPS. Responses are JSON unless noted otherwise.

Base URLs

The legacy host emailapi.routee.net belongs to Email API v1, which is deprecated. New integrations should use Connect only.

Authentication

Every API call requires a Bearer token obtained with OAuth 2.0 client credentials:

1. Create a Connect application on go.routee.net with the Transactional Email role.
2. Exchange your Application Id and Application Secret for a token:

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

3. Include the token on every request: Authorization: Bearer {access_token}

Tokens are valid for 1 hour. When you receive HTTP 401 or 403, request a new token and retry.

See Get authenticated using your application credentials for the full OAuth guide.

Core endpoints

Full reference: Send a transactional email, Search email tracking, Get email tracking.

Send paths

You can send email in two ways — both use the same Connect application credentials and appear in the same delivery logs:

See Email — HTTP API vs SMTP relay to choose the right path.

Next steps

1. Setting up your account — verify domains and authorized senders
2. Domain & authorized senders — DNS and sender verification
3. Transactional Email — overview — send and track workflow