OMA RESTful APIs
The OMA RESTful APIs provide a standardized approach to interacting with network services using the REST architectural style. These APIs are designed with an HTTP protocol binding, where API operations are mapped to standard HTTP methods such as GET, POST, PUT, and DELETE. This enables seamless integration with web applications, cloud services, and mobile networks.
OMA RESTful APIs cover a wide range of network capabilities, including address book management, messaging, call handling, presence, payment, multimedia services, and more. By leveraging these APIs, developers can build scalable and interoperable applications that adhere to industry best practices.
Below is a comprehensive list of OMA RESTful APIs, detailing their specifications and usage.
API Name | HTTP Protocol Binding |
---|---|
Address Book |
|
Address List Management |
|
Anonymous Customer Reference Management |
|
Audio Call |
|
Audio Call |
|
Authorization Framework for Network APIs |
|
Bot Management |
|
Call Notification |
|
Call Notification |
|
Capability Discovery |
|
Chat |
|
Common (ParlayREST specific part) |
|
Communication Patterns |
|
Converged Address Book |
|
Device Capabilities |
|
Device Capabilities |
|
Device Management Client Side API Framework |
|
File Transfer |
|
Image Share |
|
Message Broadcast |
|
Messaging |
|
MultiMedia Messaging |
|
Navigation Service Framework |
|
Network Message Store |
|
Notification Channel |
|
OneAPI Profile of ParlayREST V 2.0 |
|
OneAPI Profile of RESTful Network APIs |
|
OneAPI Profile of RESTful Network APIs |
|
Payment |
|
Payment |
|
Presence |
|
Presence |
|
Quality of Service |
|
RCS Profile |
|
RCS Profile of ParlayREST V 1.0 |
|
RCS-e Profile |
|
Rich Comunications |
|
Roaming Provisioning 1.0 |
|
Services User Profile Management |
|
Short Messaging |
|
Short Messaging |
|
Terminal Location |
|
Terminal Location |
|
Terminal Status |
|
Terminal Status |
|
Third Party Call |
|
Third Party Call |
|
Twinning |
|
Video Share |
|
WebRTC Signaling |
|
Zonal Presence |
|