Route Mobile SMS API
Route Mobile's core A2P SMS platform — single, bulk, scheduled and personalised SMS submission over HTTPS, credit checks, account details, OTP generation and verification, DND/whitelist management, coverage map download, and pre-built submission endpoints for the MoEngage and WebEngage marketing platforms. 14 documented operations across the Message Sending, Account, OTP and Integrations tags. Authentication is via username and password query parameters, with a static Authorization header token used for the third-party integration endpoints.
Route Mobile SMS API is one of 6 APIs that Route Mobile publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include SMS, A2P Messaging, and OTP. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.
This API exposes 14 operations across 14 paths, organized into 4 resource areas, and defines 7 schemas. It is described by OpenAPI 3.0.3, at version 1.0.0.
Requests are made against 4 base URLs: https://api.rmlconnect.net, https://api.rmlconnect.net:8443, http://api.rmlconnect.net, https://client.rmlconnect.net.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 1
Route Mobile SMS API declares
1 security scheme
for authenticating requests.
An API key is passed in the header as Authorization (AuthorizationToken).
AuthorizationToken— Static authorization token provided by Route Mobile. Used for Moengage and Webengage integrations.
Paths & Operations 14
Across 14 paths, the API surfaces 14 operations — 11 GET, 3 POST. They span 4 resource areas: Message Sending, Account, OTP, Integrations. Each is listed below with its method, path, parameters, and response codes.
APIs for submitting SMS messages.
APIs for account management, credit queries, and authentication tokens.
APIs for OTP generation and verification.
APIs for third-party platform integrations.
Schemas 7
The contract defines 7 schemas that model the data the API accepts and returns. The most detailed are SmsItem (7 properties), MoengageResponse (4 properties), Metadata (3 properties), SmsData (3 properties). Each schema is shown below with its type and property counts.
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from Route Mobile 5
Other APIs Route Mobile publishes across the network.
This is an independent, third-party profile of Route Mobile SMS API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.