How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Route Mobile Integrations API

APIs for third-party platform integrations.

Route Mobile Integrations 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 Integration. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 2 operations across 2 paths, and defines 5 schemas. It is described by OpenAPI 3.2.0, 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.

2 operations 2 paths 5 schemas 2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Base URL
https://api.rmlconnect.net
Authentication
API Key
Resource Areas
1

Authentication & Security 1

Route Mobile Integrations 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 2

Across 2 paths, the API surfaces 2 operations — 2 POST. Each is listed below with its method, path, parameters, and response codes.

Integrations 2

APIs for third-party platform integrations.

POST
/bulksms/custommsgsubmit
Moengage Integration
submitMoengageSms 3 params → 200401500
POST
/bulksms2346/sendjsonsms
Webengage Integration
submitWebengageSms body → 200400401500

Schemas 5

The contract defines 5 schemas that model the data the API accepts and returns. The most detailed are MoengageResponse (4 properties), SmsData (3 properties), Metadata (3 properties), WebengageRequest (3 properties). Each schema is shown below with its type and property counts.

WebengageRequest
object
3 properties 3 required
Metadata
object
3 properties 3 required
MoengageResponse
object
4 properties
WebengageResponse
object
1 property
SmsData
object
3 properties 3 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

route-mobile-integrations-api-openapi.yml Raw ↑

Other APIs Route Mobile publishes across the network.

Route Mobile Enterprise Voice 2.0 API
Route Mobile Account API
Route Mobile Account Management API
Route Mobile Accounts API
Route Mobile Authentication API
Route Mobile Bulk Campaigns API
Route Mobile Bulk Upload Campaign API
Route Mobile Callback API
Route Mobile Capability Check API
Route Mobile Catalog Management API
Route Mobile File Server API
Route Mobile Login API
Where this information came from

This is an independent, third-party profile of Route Mobile Integrations 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.