Blast RCS to Audience
Authentication
Request
Array of RCS agent IDs to send from. Each must be prefixed with agent_.
Messages will be evenly distributed across these agents.
Note: Test agents cannot be used for blasts.
Limit: 1 min
Array of RCS agent IDs to send from. Each must be prefixed with agent_.
Messages will be evenly distributed across these agents.
Note: Test agents cannot be used for blasts.
Limit: 1 min
Send an RCS message to all contacts in an audience.
Messages are distributed evenly across the provided RCS agents for load balancing. Requires active RCS agents and recipient devices that support RCS Business Messaging.
Use the optional schedule parameter in options to schedule the blast for future delivery. When scheduled, the response will contain a scheduleId instead of blast details.
The audience ID to send the blast to. This identifier is a string that always begins with the prefix aud_, for example: aud_abc123.
You can create an audience via the dashboard or API.
SMS/MMS fallback message to send if the RCS message fails to deliver.
When a recipient’s device doesn’t support RCS or the RCS message cannot be delivered, this fallback message will be sent as SMS or MMS instead. The fallback is sent from the specified phone number.
Note: At least one of
textormediaUrlsmust be provided. Fallback messages require a verifiedfromphone number with SMS/MMS sending capabilities. Note: You will not be charged for the fallback message, only the original RCS message will be charged.
Successfully queued or scheduled the RCS blast.
scheduleId and the schedule configuration.