Create Test Agent
Create a new RCS test agent for development and testing.
Overview
Test agents let you build and test full RCS functionality — rich cards, carousels, buttons, quick replies, and media messages — without going through the full carrier review process. Messages from test agents can only be sent to whitelisted phone numbers.
Limits
- Maximum 5 test agents per account.
Image Requirements
| Image | Format | Max Size |
|---|---|---|
| Logo | JPEG, PNG | 50 KB |
| Hero | JPEG, PNG | 200 KB |
After Creation
Once your test agent is created, you'll need to:
- Whitelist test phone numbers using
POST /rcs/test/agents/{agentId}/whitelist. - Accept the tester invite on each whitelisted device.
- Send messages using
POST /messages/send/rcswith the returned agent ID as thefromfield.
2-Minute Cooldown
After creating a test agent, there is a mandatory 2-minute cooldown before you can whitelist phone numbers. This is a requirement imposed by Google's RBM platform.
Request Body
application/json
TypeScript Definitions
Use the request body type in TypeScript.
Request body for creating a new RCS test agent.
Test agents allow you to develop and test RCS functionality before going through carrier review. Each account can create up to 5 test agents.
displayNamestringDisplay name of the agent shown to users in RCS conversations. Must be between 1 and 40 characters.
descriptionstringShort description of what the agent does. Shown to users in the agent's profile. Must be between 1 and 100 characters.
logoUrlstringURL to the agent's logo image. Displayed as the agent's avatar in conversations.
Requirements:
- Format: JPEG or PNG
- Max file size: 50 KB
- Recommended: Square aspect ratio
heroUrlstringURL to the agent's hero banner image. Displayed at the top of the agent's profile.
Requirements:
- Format: JPEG or PNG
- Max file size: 200 KB
- Recommended: Landscape aspect ratio
Contact phone numbers displayed on the agent's profile. At least 1 and up to 3 entries.
Contact email addresses displayed on the agent's profile. At least 1 and up to 3 entries.
Website links displayed on the agent's profile. At least 1 and up to 3 entries.
privacyUrlstringURL to the agent's privacy policy.
termsUrlstringURL to the agent's terms and conditions.
colorstringThe agent's brand color as a hex color code. Used for UI accents in the RCS conversation. Must have sufficient contrast with white for accessibility.
isConversationalbooleanWhether the agent supports two-way conversations. Set to true if the agent
will respond to user messages. Set to false for send-only agents (e.g., notifications).
agentUseCasestringOptionalThe primary use case for the RCS agent. This helps carriers understand the purpose of the agent during review.
TRANSACTIONAL— Order confirmations, shipping updates, appointment reminders, and similar transactional notifications.PROMOTIONAL— Marketing messages, offers, discounts, and promotional content.OTP— One-time passwords and verification codes.MULTI_USE— A combination of transactional, promotional, and/or OTP messaging.
"TRANSACTIONAL""PROMOTIONAL""OTP""MULTI_USE"Response Body
application/json
application/json
application/json
application/json
application/json