Update Test Agent
Update an existing RCS test agent's configuration.
All fields are optional — only include the fields you want to update.
Image Requirements
If updating images, the same requirements apply as when creating an agent:
| Image | Format | Max Size |
|---|---|---|
| Logo | JPEG, PNG | 50 KB |
| Hero | JPEG, PNG | 200 KB |
2-Minute Cooldown
After updating 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.
Path Parameters
agentIdstringThe RCS agent ID (must be prefixed with agent_).
Request Body
application/json
TypeScript Definitions
Use the request body type in TypeScript.
Request body for updating an existing RCS test agent.
All fields are optional — only include the fields you want to update. At least one field must be provided.
displayNamestringOptionalDisplay name of the agent shown to users in RCS conversations. Must be between 1 and 40 characters.
descriptionstringOptionalShort description of what the agent does. Must be between 1 and 100 characters.
logoUrlstringOptionalURL to the agent's logo image.
Requirements:
- Format: JPEG or PNG
- Max file size: 50 KB
- Recommended: Square aspect ratio
heroUrlstringOptionalURL to the agent's hero banner image.
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.
privacyUrlstringOptionalURL to the agent's privacy policy.
termsUrlstringOptionalURL to the agent's terms and conditions.
colorstringOptionalThe agent's brand color as a hex color code. Must have sufficient contrast with white.
isConversationalbooleanOptionalWhether the agent supports two-way conversations.
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
application/json