Rich Communications Services (RCS) Messaging-as-a-Platform (MaaP) enables a chatbot to interact with a chatbot platform 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 90-days. When obtaining MaaP credentials, the webhook for your chatbot is registered and associated with those credentials. A bot ID is generated with your credentials and can be used to initiate a messaging session from the RCS Client Simulator.
RCS MaaP Simulator service enables a chatbot to authenticate with a simulated chatbot platform 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 generated.
RCS MaaP Simulator Credentials
The bot ID, client ID and client secret for use in your chatbot application are dynamically generated on this webpage.
Enter your chatbot name and application webhook, then click the below button to register the webhook and retrieve your credentials.
| Chatbot | |
| Bot ID: |
autogenerated
|
| Chatbot name: | |
Optional: Name to describe your chatbot application. | |
| Chatbot webhook: | |
Optional: Webhook for MaaP events to your chatbot application. | |
| Chatbot platform | |
| OAuth and MaaP: | rcsmaapsim.melroselabs.com |
| Port: | 443 (HTTPS) |
| Client ID: | autogenerated |
| Client Secret: |
autogenerated
|
Use the above credentials in your chatbot application with the RCS MaaP Simulator service. If you need any help, send us a support request.
Registering an application webhook enables your chatbot application to receive messages via the RCS MaaP Simulator from the RCS Client Simulator and events (e.g. message status updates, typing indicators).
RCS Client Simulator
RCS Messaging Client Configuration
 | ||
|
|
|
|
||
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
| Item | Path | Functional Unit/Description | Supported |
|---|---|---|---|
| Chatbot to Chatbot Platform | |||
| auth | /oauth2/v1/token | OAuth2 | YES |
| auth | /oauth2/v1/token | Basic Authentication | NO |
| capability | /rcs/bot/v1/{botId}/contactCapabilities | - | YES |
| messages | /rcs/bot/v1/{botId}/messages | - | YES |
| message status | /rcs/bot/v1/{botId}/messages/{msgId}/status | - | YES |
| Chatbot Platform to Chatbot | |||
| webhook | - | message from user | YES * |
| - | - | isTyping notification from user | YES * |
| - | - | message status update | YES |
| - | - | uploaded file status update | - |
| - | - | response to suggested reply or action | YES * |
| - | - | alias link command | - |
| - | - | new user | YES * |
* when using Melrose Labs RCS Client Simulator or the RCS MaaP Simulator API
RCS Client Support (RCS Client Simulator)
| Item | Path | Functional Unit/Description | Supported |
|---|---|---|---|
| RCS MaaP events to Chatbot from RCS Client | |||
| - | - | message from user | YES |
| - | - | isTyping notification from user | YES |
| - | - | message status update | - |
| - | - | uploaded file status update | - |
| - | - | response to suggested reply or action | YES |
| - | - | alias link command | - |
| - | - | new user | YES |
| RCS messages supported - Chatbot to RCS Client | |||
| - | - | textMessage | YES |
| - | - | fileMessage | - |
| - | - | audioMessage | - |
| - | - | geoLocationPushMessage | - |
| - | - | richcardMessage | Partial |
| - | - | suggestedChipList | YES |
| RCS messages supported - RCS Client to Chatbot | |||
| - | - | textMessage | YES |
| - | - | fileMessage | - |
| - | - | audioMessage | NO |
| - | - | geoLocationPushMessage | - |
Simulator API
| Event | Description | Path | Example |
|---|---|---|---|
| Simulate RCS operations to Chatbot from Chatbot Platform/mobile user | |||
| message from user | /sim/messages/{botId} | POST request with bot ID in the URL path and JSON payload containing message text and originating mobile number. No authentication required. | curl -v -H "Content-Type: application/json" https://rcsmaapsim.melroselabs.com/sim/messages/bot789383 -d '{"RCSMessage":{"textMessage":"hello world!"},"messageContact":{"userContact":"+447964847040"}}' |
| isTyping notification from user | /sim/messages/{botId} | POST request with bot ID in the URL path and JSON payload. No authentication required. | curl -v -H "Content-Type: application/json" https://rcsmaapsim.melroselabs.com/sim/messages/bot789383 -d '{"RCSMessage":{"isTyping":"active"},"messageContact":{"userContact":"+447964847040"}}' |
| message status update | /sim/messages/{botId} | POST request with bot ID in the URL path and JSON payload. No authentication required. | curl -v -H "Content-Type: application/json" https://rcsmaapsim.melroselabs.com/sim/messages/bot789383 -d '{"RCSMessage":{"status":"displayed"},"messageContact":{"userContact":"+447964847040"}}' |
| response to suggested reply or action | /sim/messages/{botId} | POST request with bot ID in the URL path and JSON payload. No authentication required. | curl -v -H "Content-Type: application/json" https://rcsmaapsim.melroselabs.com/sim/messages/bot789383 -d '{"RCSMessage":{"suggestedResponse":...},"messageContact":{"userContact":"+447964847040"}}' |
Service snapshot
- Test RCS applications and infrastructure without RCS cost or risk
- Messaging-as-a-Platform (MaaP) v1.0
- A2P and P2A
- Web browser RCS client