RCS
Blooio RCS registration. RCS messages arrive in the Google Messages app from a verified business sender, with its name, logo, and colors, instead of a phone number. The organization registers one brand (the business), then one or more senders (each a branded profile people message). Google verifies a sender's brand, testers try it on their own phones, and carriers approve its launch; it can message the testers once it's `verified` and anyone once it's `live`. Each sender is an `rcs_business` channel: send from its channel id or alias with `POST /messages`. Once submitted, a sender's name, logo, and banner and the brand's point of contact change by paid change request. Submitting, launching, and change requests bill the organization's SMS, Voice & RCS subscription, so they need a card on file. Status changes arrive as `registration.rcs_brand.updated`, `registration.rcs_sender.updated`, and `registration.rcs_change.updated` webhooks. OAuth apps need `numbers:read` to read and `numbers:manage` to register. See the Blooio RCS guide.
- Upload RCS asset
- Get RCS brand
- Put RCS brand
- Request RCS brand change
- List RCS changes
- Cancel RCS change
- List RCS senders
- Create RCS sender
- Get RCS sender
- Update RCS sender
- Remove RCS sender
- Request RCS sender change
- Launch RCS sender
- Submit RCS sender
- List RCS test devices
- Add RCS test device
- Remove RCS test device