Route Mobile Messaging API
Send template messages (marketing, utility, authentication) and session messages (text, media, interactive, payments, flows) to individual recipients.
Route Mobile Messaging API is one of 34 APIs that Route Mobile publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include Messaging. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.
This API exposes 7 operations across 7 paths, and defines 68 schemas. It is described by OpenAPI 3.2.0, at version 1.8.0.
Requests are made against a single base URL, https://apis.rmlconnect.net.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 1
Route Mobile Messaging API declares
1 security scheme
for authenticating requests.
It accepts HTTP bearer tokens (JWT) (BearerAuth).
By default, every request must be authenticated.
BearerAuth— JSON Web Token obtained from the Login API. Include the token in the Authorization header as Bearer . Tokens expire after one hour by default.
Paths & Operations 7
Across 7 paths, the API surfaces 7 operations — 1 DELETE, 1 GET, 1 PATCH, 4 POST. Each is listed below with its method, path, parameters, and response codes.
Send template messages (marketing, utility, authentication) and session messages (text, media, interactive, payments, flows) to individual recipients.
Schemas 68
The contract defines 68 schemas that model the data the API accepts and returns. The most detailed are SendSessionPaymentPayU (7 properties), SendSessionFlow (7 properties), SendSessionPaymentLink (7 properties), SendSessionPaymentWithCatalog (7 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 12
Other APIs Route Mobile publishes across the network.
This is an independent, third-party profile of Route Mobile Messaging 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.