RCS Business Messaging
AT&T's API allows access for previously approved Aggregators to send RCS business Messages on behalf of a Brand, to AT&T users.
home
The Rich Communication Services (RCS) API provided by AT&T enables external consumers to leverage advanced messaging capabilities to communicate with RCS clients on mobile devices. Here's an overview of the key features and functionalities supported by the RCS API:
Key Features of AT&T's RCS API
- Sending Messages:Text Messages: Send rich text messages that can include multimedia content such as images, videos, and audio files.
- Getting Phone Capabilities:Capability Discovery: Query the capabilities of a recipient's device to determine whether it supports RCS features. This includes checking if the device can receive rich media, participate in group chats, and more. This enables receiving real-time updates on the capabilities of contacts as they change or as they become available.
- Revoking Messages:Message Recall: Ability to revoke or delete sent messages before they are read by the recipient. This feature is useful for correcting mistakes or retracting sensitive information.
- RCS Supported Events:Typing Indicators: Send notifications when an agent is typing a message. This enhances real-time communication by indicating active engagement.Read Receipts: Notify senders when their messages have been read by the agent, including timestamps for when the message was read.
- Bulk Get Capabilities is not supported!
API Integration and Usage
- Authentication: Secure access to the RCS API through OAuth 2.0, ensuring that only authorized applications can interact with the service.
- Endpoints: A set of RESTful API endpoints for performing various operations such as sending messages, querying device capabilities, revoking messages, and managing event notifications.
- Payload Formats: JSON is used for request and response payloads, providing a standardized and easy-to-parse format for data exchange.
- Rate Limiting: Implemented to ensure fair usage and prevent abuse, with specific limits on the number of API calls per minute/hour.
- Content Urls: For content urls in messages, Agents/Aggregators shall upload the content directly to google and use Google urls on message sent with this API to AT&T .
Benefits of Using AT&T's RCS API
- Enhanced User Experience: Leverage rich media and interactive messaging features to create more engaging and dynamic user interactions.
- Real-Time Communication: Improved communication with real-time indicators and status updates, making conversations more fluid and responsive.
- Broad Compatibility: Support for a wide range of devices and RCS clients, ensuring broad reach and compatibility across different platforms.
- Secure and Reliable: Built with robust security measures and reliable delivery mechanisms to ensure that messages are transmitted safely and efficiently.
For more information on integrating with AT&T's RCS API, including detailed documentation and support resources, please visit the AT&T Developer Portal.
***The API Schema presented in this asset is aligned with Google RBM response as of date Nov 20 2024
Differences from Google API
- AT&T message Request has added new properties to support different callback url
- on creation of a message or event, the AT&T message/event id is returned in body