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

Aeris IoT Accelerator SMS Messaging API

RESTful SMS messaging API for sending mobile-terminated SMS to devices, retrieving delivery status, and retrieving inbound mobile-originated messages for a registration. The contract states it is based on the OneAPI SMS interface and OMA REST NetAPIs v1, and uses the standard /smsmessaging/v1/outbound/{senderAddress}/requests resource shape. Authenticates with HTTP Basic.

This API exposes 3 operations across 3 paths, organized into 3 resource areas, and defines 10 schemas. It is described by OpenAPI 3.0.3, at version v2.

Requests are made against a single base URL, https://sms.iot-api.aeris.com/dcpapi/smsmessaging/v1.

3 operations 3 paths 10 schemas 2 GET1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.3
API Version
v2
Base URL
https://sms.iot-api.aeris.com/dcpapi/smsmessaging/v1
Authentication
HTTP Basic
Resource Areas
3

Authentication & Security 1

Aeris IoT Accelerator SMS Messaging API declares 1 security scheme for authenticating requests. It accepts HTTP basic authentication (BasicAuth). By default, every request must be authenticated.

Paths & Operations 3

Across 3 paths, the API surfaces 3 operations — 2 GET, 1 POST. They span 3 resource areas: sendSMS, querySMS, retrieveSMS. Each is listed below with its method, path, parameters, and response codes.

sendSMS 1
POST
/outbound/{senderAddress}/requests
Sends an SMS message to one or more devices
sendSMS 2 params body → 201400401403404503
querySMS 1
GET
/outbound/{senderAddress}/requests/{requestId}/deliveryInfos
Queries the delivery status of an SMS.
querySMS 3 params → 200400401403404503
retrieveSMS 1
GET
/inbound/registrations/{registrationID}/messages
Retrieves an SMS sent to a web application.
retrieveSMS 3 params → 200400401403404503

Schemas 10

The contract defines 10 schemas that model the data the API accepts and returns. The most detailed are OutboundSMSMessageRequest (9 properties), InboundSMSMessage (7 properties), DeliveryInfoList (2 properties), DeliveryInfo (2 properties). Each schema is shown below with its type and property counts.

RequestError
object
1 property
InboundSMSMessageRequest
object
1 property
InboundSMSMessage
object
7 properties
DeliveryInfo
object
2 properties 2 required
DeliveryInfoList
object
2 properties 2 required
DeliveryInfoObject
object
1 property
OutboundSMSBinaryMessage
object
1 property 1 required
OutboundSMSMessageRequest
object
9 properties 2 required
OutboundSMSMessageRequestHolder
object
1 property 1 required
OutboundSMSTextMessage
object
1 property 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

aeris-sms-messaging-api-openapi.yaml Raw ↑
Where this information came from

This is an independent, third-party profile of Aeris IoT Accelerator SMS 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.