Routeon SMS Overview

Routeon SMS lets you send text messages worldwide through a single REST API — one-off transactional messages and OTP codes via POST /messages, and bulk marketing campaigns via the Broadcast API — with delivery tracking over webhooks and detailed per-message delivery records (EDRs). SMS is channel 1 of the omnichannel Routeon CPaaS platform: the same API and the same integration also cover RCS, Viber, WhatsApp, Telegram Gateway, Email, Push and other channels, so an SMS integration is a head start on every other channel.

What you can build with it

  • Transactional notifications — order confirmations, alerts, reminders. One POST /messages can name up to 100 comma-separated numbers in contact.
  • OTP / verification codes — send one-time codes with isOtp: true so the message body is masked in logs and reports.
  • Marketing / bulk SMS campaigns — send one message to your whole contact base through the Broadcast API, launched from a pre-approved template, immediately or on schedule.
  • Contact-base management — import and enrich recipients with tags and attributes through the Recipients API, then target campaigns by tag or filter.
  • Two-way messaging — receive inbound (mobile-originated) replies from recipients as message webhook events pushed to your endpoint.
  • Delivery tracking — per-message lifecycle (sent → delivered / failed / undeliverable) via messageStatus webhooks, plus EDR reports (GET /edrs) with operator status, timestamps and final cost for reconciliation.

What it does — and does not — do

Does:

  • Send an SMS (POST /messages, channel 1) with free-form text in payload.text. contact accepts up to 100 comma-separated numbers (digits, country code, no +).
  • Run bulk campaigns through the Broadcast API. A saved template is optional: POST /broadcast/broadcasts can carry the text in payload (contentPattern). Templates still support {{attribute.name}} personalization and scheduled or immediate launch. Marketing text may need operator approval before delivery.
  • Report delivery asynchronously: the send call returns immediately with a messageId; statuses arrive via webhook or are pulled from GET /edrs.
  • Manage contacts (import, tags, attributes, filters) via the Recipients API.
  • Expose account balance (GET /balance) and per-message pricing (rate / finalCost on each EDR).
  • Manage Sender ID templates through the sender API (GET /senders; Alaris sms_sender). Operator approval of a live sender is still completed in the Client portal and reflected in status.

Does not:

  • No unapproved custom Sender IDs. Your own Sender ID must be registered and approved before use, and approval times vary by country and operator. (Without one, a generic default sender is used.)
  • No rate-card endpoint. Pricing is visible per message after the fact (rate / finalCost in EDRs) and as your account balance (GET /balance).

How it works (10,000 ft)

  1. Account — your account manager sends an invitation link; you create credentials and sign in to the Client portal at https://client.routeon.io/.
  2. API key — in the portal under API Accesses, create a key and select scopes: omni-api (single messages), Broadcasts (campaigns), Recipients (contacts). The key is passed on every request in the X-API-Key header; it works only with the scopes you selected. All requests go to https://client.routeon.io/api/v1.
  3. Sender ID (optional but recommended for production) — register your own sender name under Assets → Sender IDs and submit it for approval. Until it is Active, a generic default sender is used.
  4. Send — POST /messages with channel: 1, the recipient number (digits, no +), and payload.text. The response returns a messageId.
  5. Track — receive messageStatus events on your webhook URL, or pull EDR records with GET /edrs for operator status, timestamps and cost.
  6. Balance — check remaining funds any time with GET /balance.

Two alternatives to the REST API:

  • SMPP — a persistent telecom-protocol connection for high-volume sending (transceiver bind, GSM 03.38 / UCS2 encoding). Request credentials from your account manager and provide a static IP for whitelisting.
  • Client portal — no-code sending: create a sender, upload contacts, build a campaign from a template and launch or schedule it, all in the browser.

Full endpoint reference: Routeon Developer Portal. Support: contact your account manager.

Next step

→ Quickstart: send your first SMS