Guides

Task-shaped recipes for the jobs most integrations start with. Each one is self-contained: a goal, its prerequisites, numbered steps with copy-pasteable requests and the responses to expect, a way to confirm it worked, and a table of the failures you are most likely to hit. If you have not sent anything yet, start with the Quickstart; for the model behind these tasks, see Key Concepts.

• Verify a sending domain — choose a provider, publish DNS records, verify, and follow the warmup ramp
• Send a transactional email — prepare a template, send now or later, cancel, send a batch, track the result
• Send OTP codes — request and verify one-time passcodes
• Import contacts — custom fields, single contacts, bulk import, list membership, data export
• Segment your audience — build, preview, and save dynamic segments
• Upload an image asset — presign, upload, confirm, and use the CDN URL in a template
• Send your first campaign — template to launch to results
• Receive webhooks — subscribe, verify signatures, survive retries and pauses

All examples use the base URL https://emails.routeon.io/api/v1 and an API key created in the customer portal at https://emails.routeon.io (section API keys), shown as <API_KEY>. Values in angle brackets (<DOMAIN_ID>, <FUTURE_ISO8601_TIMESTAMP>, …) are placeholders to replace with your own.

Error codes appear in one of two places in the error envelope: meta.details.code, or the message of an entry in meta.validation_error. The tables in these guides name the code; check both places when you branch on it. The full list is in Errors.