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 Sending Domains API

Add, verify, list, and delete sending domains

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

This API exposes 5 operations across 5 paths, and defines 8 schemas. It is described by OpenAPI 3.2.0, at version 1.0.0.

Requests are made against a single base URL, https://api.sendclean.net/v1.0.

5 operations 5 paths 8 schemas 5 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
Resource Areas
1

Paths & Operations 5

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

Sending Domains 5

Add, verify, list, and delete sending domains

POST
/settings/addSendingDomain
Add a sending domain
addSendingDomain body → 200
POST
/settings/checkSendingDomain
Verify DKIM and SPF records
checkSendingDomain body → 200
POST
/settings/verifySendingDomain
Verify sending domain via email
verifySendingDomain body → 200
POST
/settings/listSendingDomain
List sending domains
listSendingDomains body → 200
POST
/settings/deleteSendingDomain
Delete a sending domain
deleteSendingDomain body → 200

Schemas 8

The contract defines 8 schemas that model the data the API accepts and returns. The most detailed are SendingDomainListEntry (5 properties), CheckSendingDomainResponse (5 properties), ErrorResponse (4 properties), SuccessResponse (2 properties). Each schema is shown below with its type and property counts.

ListSendingDomainResponse
object
2 properties
CheckSendingDomainResponse
object
5 properties
DomainRequest
SuccessResponse
object
2 properties
AuthFields
object
2 properties 2 required
ErrorResponse
object
4 properties
VerifySendingDomainRequest
SendingDomainListEntry
object
5 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

route-mobile-sending-domains-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 Integrations API
Where this information came from

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