Rich Communications Services (RCS) Messaging-as-a-Platform (MaaP) enables a chatbot to interact with a chatbot server to send and receive messages between the chatbot and a user's mobile device. The RCS MaaP Simulator service simulates messaging between a chatbot and a user's mobile device, with the service performing as the chatbot platform that the chatbot application uses to communicate using RCS.
Credentials for using the RCS MaaP Simulator service can be obtained below and are valid for 10-days. When obtaining MaaP credentials, the webhook for your chatbot is registered and associated with those credentials. A bot name is generated with your credentials and can be used to initiate a messaging session from the RCS client.
RCS MaaP Simulator service enables a chatbot to authenticate with the chatbot server using OAuth2 and perform MaaP operations. A simple web-based RCS client can be used to simulate a user's mobile for sending and receiving messages. Messages received from the RCS client are passed to the chatbot webhook registered with the service when MaaP credentials were obtained.
RCS MaaP Simulator Credentials
The bot name, client ID and client secret are dynamically generated on this webpage. Enter your chatbot webhook and click the below button to register webhook and retrieve your credentials.
Optional: Webhook for MaaP callbacks to your chatbot application.
|OAuth and MaaP Server:|
Use the above credentials with the RCS MaaP Simulator service. If you need any help or have any suggestions for improving the service, then send us a support request.
Our simple web-based RCS client can be used to simulate a user's mobile for sending and receiving messages. Messages received from the RCS client are passed to the chatbot webhook registered with the service when MaaP credentials were obtained.
Developers needing to add RCS support to an application can write code to send RCS with MaaP and use the RCS MaaP Simulator to test.
Melrose Labs RCS MaaP Simulator
MaaP API Support
RCS Client Support
- Test RCS applications and infrastructure without RCS cost or risk
- Messaging-as-a-Platform (MaaP) v1.0
- A2P and P2A
- Web-base RCS client