Get RCS Campaign by ID
Authentication
Path parameters
Unique identifier of the RCS campaign. Must begin with the prefix rcs_.
Response
Current review status of the campaign.
INCOMPLETE: Not submitted.
IN REVIEW: Being reviewed by carriers.
VERIFIED: Approved and ready to send messages.
FAILED: Issues and errors related to the campaign’s details.
Unique identifier for the campaign. This identifier is a string that always begins with the prefix rcs_, for example: rcs_1234567890.
List of what the agent might say to users. See the Expected Agent Responses section for requirements.
Details on how opt-in is acquired. If it is done through a website or app, provide the link. See the Opt-In Terms and Conditions section for requirements.
Type of message the agent sends.
OTP: One time passwords or verification codes.
TRANSACTIONAL: Account updates, alerts, or notifications.
PROMOTIONAL: Marketing, sales, or offers.
MULTI_USE: Mixed message types.
Description of the agent’s purpose, shown to carriers for approval. See the Carrier Description section for requirements.
Explanation of how the agent is triggered. This includes how the first message is delivered, whether messages follow a schedule or triggered by user actions, and any external triggers. See the Agent Triggers section for requirements.
Description of all agent interactions, including primary and secondary use cases. See the Interaction Description section for requirements.
Whether the agent supports conversational flows or respond to P2A messages from the users. Set to false for one-way messages from agent to user.
Required text that appears next to the opt-in checkbox for your opt-in form. This checkbox has to be unchecked by default. See the CTA Language section for requirements.
Instructions on how an external reviewer can trigger messages and an example flow from the agent. This is usually an inbound text message to the agent that will start a flow of messages between the agent and the user. See the Demo Trigger section for requirements.

