Overview

MRC exposes a deliberately small, phone-number-first surface for compliance-grade texting. Three endpoints cover the whole MVP:

Operation	Purpose	Scope
`POST /mrc/messaging/messages`	Send an SMS from the advisor’s MyRepChat number (guide)	`mrc.messaging.write`
`POST /mrc/messaging/consent-requests`	Send the firm’s consent-request SMS to one or more phone numbers (guide)	`mrc.messaging.write`
`GET /mrc/messaging/consents`	Read a contact’s consent state by `?phone=` (or `?memberId=`) (guide)	`mrc.messaging.read`

Every request carries an OAuth Bearer token (OAuth Integration Guide) and your usage-plan x-api-key header. Start with the Integration Guide — it walks the canonical send → consent → poll → resend loop end to end, including the error model and polling cadence. The generated reference below it documents every field, sourced directly from the API’s own contract definitions.

Upcoming

Delivery status — GET on a sent message’s status by messageId.
Structured failure reason codes — an additive failureDetails[] alongside today’s human-readable failures[] strings.
Media (MMS) — fast-follow after the SMS launch.

OAuth

Guides

Errors

API Reference

Upcoming

​Upcoming

Upcoming