Developers

API reference

A predictable REST API for inbound email. Read messages, manage domains and routing rules, and inspect delivery logs — all over HTTPS with JSON responses.

Authentication

Authenticate every request with a secret API key sent as a bearer token. Keys are scoped to a workspace and can be rotated at any time from the dashboard.

curl https://api.inletops.com/v1/messages \
  -H "Authorization: Bearer sk_live_…"

The base URL is https://api.inletops.com/v1. All requests must be made over HTTPS; plain HTTP is rejected.

Messages

A message is a single inbound email, parsed into a stable object with headers, decoded body, and extracted attachments.

GET/v1/messages

List messages for the workspace, most recent first. Supports pagination and filtering by domain and recipient.

ParameterTypeDescription
domainstringFilter to a connected domain, e.g. acme.com.
tostringFilter by recipient address.
limitintegerPage size, 1–100. Defaults to 25.
cursorstringPagination cursor from a previous response.
GET/v1/messages/:id

Retrieve a single parsed message by its identifier.

GET/v1/messages/:id/raw

Fetch the original, unmodified MIME for a message when you need the raw bytes.

{
  "id": "msg_8Hk2…",
  "to": "invoices@acme.com",
  "from": "vendor@example.com",
  "subject": "Invoice #1042 attached",
  "attachments": [{ "filename": "invoice-1042.pdf", "size": 184203 }],
  "received_at": "2026-05-10T14:22:31Z"
}

Domains

GET/v1/domains

List connected domains and their verification status.

POST/v1/domains

Connect a new domain. The response includes the DNS records to add for verification.

Routing rules

GET/v1/routes
POST/v1/routes
DELETE/v1/routes/:id

Create rules that match on recipient, sender, subject, or content, then forward, tag, or fire a webhook.

Deliveries

GET/v1/deliveries

Inspect webhook and forwarding delivery attempts, including status, response code, and retry history. Useful for debugging and for triggering a replay.

Errors

InletOps uses conventional HTTP status codes. 2xx indicates success, 4xx indicates a problem with the request, and 5xx indicates a server-side error you can safely retry.

CodeMeaning
400Malformed request or invalid parameters.
401Missing or invalid API key.
404Resource not found.
429Rate limit exceeded — back off and retry.
Get started

Make inbound email programmable.

Turn email-driven workflows into structured, observable automation.

Try it for free