---
title: "Send RCS Message"
method: POST
path: "/messages/send/rcs"
tags: ["Messages > rcs"]
---

# Send RCS Message

`POST /messages/send/rcs`

## Request

- Base URL: `https://api.pinnacle.sh`
- URL: `https://api.pinnacle.sh/messages/send/rcs`
- Auth: API key in header `PINNACLE-API-KEY`

Send a RCS message immediately or schedule it for future delivery. <br>

Requires an active RCS agent and recipient devices that support RCS Business Messaging.

## Request body

- union
  - SendRcsText
    - `from` string, required: Your RCS agent ID which must be prefixed with 'agent_'.
    - `fallback` FallbackMessage: SMS/MMS fallback message to send if the RCS message fails to deliver. When a recipient's device doesn't support RCS, 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 `text` or `mediaUrls` must be provided. Fallback messages require a verified `from` phone number with SMS/MMS sending capabilities. > **Billing:** You will be charged the standard SMS or MMS rate for the fallback message. The original RCS message will not be charged if the fallback is sent instead.
      - `from` string, required: Phone number to send the fallback message from in E.164 format. Must be a verified phone number with SMS/MMS sending capabilities. Sandbox numbers cannot be used for fallbacks. The phone number must be connected to an active toll-free or 10DLC campaign.
      - `text` string: Text content for the fallback message. At least one of `text` or `mediaUrls` must be provided. If `mediaUrls` is empty and the text fits within SMS segment limits, the fallback will be sent as SMS. Otherwise, it will be sent as MMS. You will only be billed for the message sent.
      - `mediaUrls` string[]: Media file URLs to include in the fallback MMS message. See [supported media types](https://app.pinnacle.sh/supported-file-types?type=MMS). If provided, the fallback will be sent as MMS. Otherwise, it will be sent as SMS (if text fits within segment limits). At least one of `text` or `mediaUrls` must be provided.
    - `options` SendRichMessageOptions: Configure how your RCS message is sent and tracked.
      - `schedule` ScheduleSchema: Define when and how your message should be sent.
        - `sendAt` string, required: The date and time you want your message to be sent. - Use [ISO 8601 format](https://en.wikipedia.org/wiki/ISO_8601), for example: `2024-12-17T14:30:00Z`. Format: `YYYY-MM-DDThh:mm` (e.g., `2024-12-25T14:30`). - This time must be at least 5 minutes in the future. - The message will be scheduled based on the `timezone` you provide. - If you set a `recurrence` schedule, this is the start date and time for the recurring schedule.
        - `recurrence` string: AWS cron expression for recurring schedules (6 fields). <br> [Learn more about cron expressions](https://docs.aws.amazon.com/eventbridge/latest/userguide/eb-scheduled-rule-pattern.html). <br> **Examples:** - `0 10 * * ? *` - Every day at 10:00 AM - `0/30 * * * ? *` - Every 30 minutes - `0 9 ? * MON-FRI *` - Every weekday at 9:00 AM - `0 12 1 * ? *` - First day of every month at noon
        - `timezone` string: IANA timezone identifier (e.g., `America/New_York`, `UTC`). <br> Defaults to `UTC` if not specified.
        - `endDate` string: Date and time when recurring messages should stop. <br> Format: `YYYY-MM-DDThh:mm`. Required if `recurrence` is set.
      - `tracking` 'ID' | 'HIDDEN': Enable tracking on sent messages. If not provided, messages are not tracked. You will not be able to react to these messages unless you provide the [options.force](./react#request.body.options.force) field. `ID` - Append an explicit ID at the end of the message for tracking. Users will see this ID. <br> `HIDDEN` - Invisible IDs are sent with messages for tracking. Will not be visible to users but will lead to slightly longer message lengths.
      - `transcode` boolean: Media files and card media will be transcoded to a supported RCS format. This adds a small delay to sending the message. Ignored for rich text messages.
      - `validate` boolean: Validate your message for any unsupported files. <br> If failed, errors will be thrown and the message will not send.
    - `to` string, required: Recipient's phone number in E.164 format.
    - `quickReplies` RichButton[]: List of interactive quick reply buttons in the message. <br><br> **Limit:** 10 max
      - union
        - object: Button that opens a URL when tapped by the recipient.
          - `type` 'openUrl', required: Discriminator value: openUrl
          - `webviewMode` 'HALF' | 'TALL' | 'FULL': Controls how the URL is displayed when the button is tapped. **Default behavior:** If not specified, the URL opens in the device's default browser. If you're sending deeplinks, you should use this mode as it will open the deeplink in the native app if it is installed. **Available modes in order of size:** - `HALF` — Half-screen webview overlay - `TALL` — Tall webview overlay - `FULL` — Full-screen webview
          - `payload` string, uri, required: The URL to open when the button is tapped. Must be a valid HTTP or HTTPS URL.
          - `title` string, required: Display text for the button.
          - `metadata` string: Optional additional data to attach to this button.
        - object: Button that initiates a phone call when tapped by the recipient.
          - `type` 'call', required: Discriminator value: call
          - `metadata` string: Optional additional data to attach to this button.
          - `payload` string, required: Phone number to call in E.164 format
          - `title` string, required: Display text for the button.
        - object: Button that sends custom data back to your application when tapped by the recipient.
          - `type` 'trigger', required: Discriminator value: trigger
          - `metadata` string: Optional additional data to attach to this button.
          - `payload` string, required: Custom data sent to your webhook when the button is tapped. Use this to identify the user's choice.
          - `title` string, required: Display text for the button.
        - object: Button that prompts the recipient to share their current location.
          - `type` 'requestUserLocation', required: Discriminator value: requestUserLocation
          - `metadata` string: Optional additional data to attach to this button.
          - `title` string, required: Display text for the button.
        - object: Button that prompts the recipient to add an event to their calendar.
          - `type` 'scheduleEvent', required: Discriminator value: scheduleEvent
          - `eventDescription` string: Detailed description for the calendar event.
          - `eventEndTime` string, required: End time in ISO 8601 format.
          - `eventStartTime` string, required: Starting time in ISO 8601 format.
          - `eventTitle` string, required: Title of the event.
          - `metadata` string: Optional additional data to attach to this button.
          - `title` string, required: Display text for the button.
        - object: Button that shares a specific location with the recipient when tapped.
          - `type` 'sendLocation', required: Discriminator value: sendLocation
          - `name` string: Optional name or label for the location that will be displayed in the map app (e.g., "Central Park", "Home Office"). If not provided, the button title will be used as the location name.
          - `latLong` RichButtonDiscriminatorMappingSendLocationLatLong, required: Geographic coordinates of the location to share.
            - `lat` number, double, required: Latitude coordinate in decimal degrees.
            - `lng` number, double, required: Longitude coordinate in decimal degrees.
          - `title` string, required: Display text for the button.
          - `metadata` string: Optional additional data to attach to this button.
    - `text` string, required: Text content of the RCS message.
  - SendRcsMedia
    - `from` string, required: Your RCS agent ID which must be prefixed with 'agent_'.
    - `fallback` FallbackMessage: SMS/MMS fallback message to send if the RCS message fails to deliver. When a recipient's device doesn't support RCS, 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 `text` or `mediaUrls` must be provided. Fallback messages require a verified `from` phone number with SMS/MMS sending capabilities. > **Billing:** You will be charged the standard SMS or MMS rate for the fallback message. The original RCS message will not be charged if the fallback is sent instead.
      - `from` string, required: Phone number to send the fallback message from in E.164 format. Must be a verified phone number with SMS/MMS sending capabilities. Sandbox numbers cannot be used for fallbacks. The phone number must be connected to an active toll-free or 10DLC campaign.
      - `text` string: Text content for the fallback message. At least one of `text` or `mediaUrls` must be provided. If `mediaUrls` is empty and the text fits within SMS segment limits, the fallback will be sent as SMS. Otherwise, it will be sent as MMS. You will only be billed for the message sent.
      - `mediaUrls` string[]: Media file URLs to include in the fallback MMS message. See [supported media types](https://app.pinnacle.sh/supported-file-types?type=MMS). If provided, the fallback will be sent as MMS. Otherwise, it will be sent as SMS (if text fits within segment limits). At least one of `text` or `mediaUrls` must be provided.
    - `options` SendRichMessageOptions: Configure how your RCS message is sent and tracked.
      - `schedule` ScheduleSchema: Define when and how your message should be sent.
        - `sendAt` string, required: The date and time you want your message to be sent. - Use [ISO 8601 format](https://en.wikipedia.org/wiki/ISO_8601), for example: `2024-12-17T14:30:00Z`. Format: `YYYY-MM-DDThh:mm` (e.g., `2024-12-25T14:30`). - This time must be at least 5 minutes in the future. - The message will be scheduled based on the `timezone` you provide. - If you set a `recurrence` schedule, this is the start date and time for the recurring schedule.
        - `recurrence` string: AWS cron expression for recurring schedules (6 fields). <br> [Learn more about cron expressions](https://docs.aws.amazon.com/eventbridge/latest/userguide/eb-scheduled-rule-pattern.html). <br> **Examples:** - `0 10 * * ? *` - Every day at 10:00 AM - `0/30 * * * ? *` - Every 30 minutes - `0 9 ? * MON-FRI *` - Every weekday at 9:00 AM - `0 12 1 * ? *` - First day of every month at noon
        - `timezone` string: IANA timezone identifier (e.g., `America/New_York`, `UTC`). <br> Defaults to `UTC` if not specified.
        - `endDate` string: Date and time when recurring messages should stop. <br> Format: `YYYY-MM-DDThh:mm`. Required if `recurrence` is set.
      - `tracking` 'ID' | 'HIDDEN': Enable tracking on sent messages. If not provided, messages are not tracked. You will not be able to react to these messages unless you provide the [options.force](./react#request.body.options.force) field. `ID` - Append an explicit ID at the end of the message for tracking. Users will see this ID. <br> `HIDDEN` - Invisible IDs are sent with messages for tracking. Will not be visible to users but will lead to slightly longer message lengths.
      - `transcode` boolean: Media files and card media will be transcoded to a supported RCS format. This adds a small delay to sending the message. Ignored for rich text messages.
      - `validate` boolean: Validate your message for any unsupported files. <br> If failed, errors will be thrown and the message will not send.
    - `to` string, required: Recipient's phone number in E.164 format.
    - `media` string, url, required: Media file URLs to send. <br> See [supported media types](https://app.pinnacle.sh/supported-file-types?type=RCS-MEDIA).
    - `quickReplies` RichButton[]: List of interactive quick reply buttons in the message. <br> `≤10`
      - union
        - object: Button that opens a URL when tapped by the recipient.
          - `type` 'openUrl', required: Discriminator value: openUrl
          - `webviewMode` 'HALF' | 'TALL' | 'FULL': Controls how the URL is displayed when the button is tapped. **Default behavior:** If not specified, the URL opens in the device's default browser. If you're sending deeplinks, you should use this mode as it will open the deeplink in the native app if it is installed. **Available modes in order of size:** - `HALF` — Half-screen webview overlay - `TALL` — Tall webview overlay - `FULL` — Full-screen webview
          - `payload` string, uri, required: The URL to open when the button is tapped. Must be a valid HTTP or HTTPS URL.
          - `title` string, required: Display text for the button.
          - `metadata` string: Optional additional data to attach to this button.
        - object: Button that initiates a phone call when tapped by the recipient.
          - `type` 'call', required: Discriminator value: call
          - `metadata` string: Optional additional data to attach to this button.
          - `payload` string, required: Phone number to call in E.164 format
          - `title` string, required: Display text for the button.
        - object: Button that sends custom data back to your application when tapped by the recipient.
          - `type` 'trigger', required: Discriminator value: trigger
          - `metadata` string: Optional additional data to attach to this button.
          - `payload` string, required: Custom data sent to your webhook when the button is tapped. Use this to identify the user's choice.
          - `title` string, required: Display text for the button.
        - object: Button that prompts the recipient to share their current location.
          - `type` 'requestUserLocation', required: Discriminator value: requestUserLocation
          - `metadata` string: Optional additional data to attach to this button.
          - `title` string, required: Display text for the button.
        - object: Button that prompts the recipient to add an event to their calendar.
          - `type` 'scheduleEvent', required: Discriminator value: scheduleEvent
          - `eventDescription` string: Detailed description for the calendar event.
          - `eventEndTime` string, required: End time in ISO 8601 format.
          - `eventStartTime` string, required: Starting time in ISO 8601 format.
          - `eventTitle` string, required: Title of the event.
          - `metadata` string: Optional additional data to attach to this button.
          - `title` string, required: Display text for the button.
        - object: Button that shares a specific location with the recipient when tapped.
          - `type` 'sendLocation', required: Discriminator value: sendLocation
          - `name` string: Optional name or label for the location that will be displayed in the map app (e.g., "Central Park", "Home Office"). If not provided, the button title will be used as the location name.
          - `latLong` RichButtonDiscriminatorMappingSendLocationLatLong, required: Geographic coordinates of the location to share.
            - `lat` number, double, required: Latitude coordinate in decimal degrees.
            - `lng` number, double, required: Longitude coordinate in decimal degrees.
          - `title` string, required: Display text for the button.
          - `metadata` string: Optional additional data to attach to this button.
  - SendRcsCard
    - `from` string, required: Your RCS agent ID which must be prefixed with 'agent_'.
    - `fallback` FallbackMessage: SMS/MMS fallback message to send if the RCS message fails to deliver. When a recipient's device doesn't support RCS, 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 `text` or `mediaUrls` must be provided. Fallback messages require a verified `from` phone number with SMS/MMS sending capabilities. > **Billing:** You will be charged the standard SMS or MMS rate for the fallback message. The original RCS message will not be charged if the fallback is sent instead.
      - `from` string, required: Phone number to send the fallback message from in E.164 format. Must be a verified phone number with SMS/MMS sending capabilities. Sandbox numbers cannot be used for fallbacks. The phone number must be connected to an active toll-free or 10DLC campaign.
      - `text` string: Text content for the fallback message. At least one of `text` or `mediaUrls` must be provided. If `mediaUrls` is empty and the text fits within SMS segment limits, the fallback will be sent as SMS. Otherwise, it will be sent as MMS. You will only be billed for the message sent.
      - `mediaUrls` string[]: Media file URLs to include in the fallback MMS message. See [supported media types](https://app.pinnacle.sh/supported-file-types?type=MMS). If provided, the fallback will be sent as MMS. Otherwise, it will be sent as SMS (if text fits within segment limits). At least one of `text` or `mediaUrls` must be provided.
    - `options` SendRichCardsOptions: Configure how your RCS message is sent and tracked.
      - `schedule` ScheduleSchema: Define when and how your message should be sent.
        - `sendAt` string, required: The date and time you want your message to be sent. - Use [ISO 8601 format](https://en.wikipedia.org/wiki/ISO_8601), for example: `2024-12-17T14:30:00Z`. Format: `YYYY-MM-DDThh:mm` (e.g., `2024-12-25T14:30`). - This time must be at least 5 minutes in the future. - The message will be scheduled based on the `timezone` you provide. - If you set a `recurrence` schedule, this is the start date and time for the recurring schedule.
        - `recurrence` string: AWS cron expression for recurring schedules (6 fields). <br> [Learn more about cron expressions](https://docs.aws.amazon.com/eventbridge/latest/userguide/eb-scheduled-rule-pattern.html). <br> **Examples:** - `0 10 * * ? *` - Every day at 10:00 AM - `0/30 * * * ? *` - Every 30 minutes - `0 9 ? * MON-FRI *` - Every weekday at 9:00 AM - `0 12 1 * ? *` - First day of every month at noon
        - `timezone` string: IANA timezone identifier (e.g., `America/New_York`, `UTC`). <br> Defaults to `UTC` if not specified.
        - `endDate` string: Date and time when recurring messages should stop. <br> Format: `YYYY-MM-DDThh:mm`. Required if `recurrence` is set.
      - `tracking` 'ID' | 'HIDDEN': Enable tracking on sent messages. If not provided, messages are not tracked. You will not be able to react to these messages unless you provide the [options.force](./react#request.body.options.force) field. `ID` - Append an explicit ID at the end of the message for tracking. Users will see this ID. <br> `HIDDEN` - Invisible IDs are sent with messages for tracking. Will not be visible to users but will lead to slightly longer message lengths.
      - `transcode` boolean: Media files and card media will be transcoded to a supported RCS format. This adds a small delay to sending the message. Ignored for rich text messages.
      - `validate` boolean: Validate your message for any unsupported files. <br> If failed, errors will be thrown and the message will not send.
      - `standalone_card` RichStandaloneCardOptions: Configure standalone card layout options for enhanced visual presentation. > **⚠️ Important Restriction** > > This option is **only valid for single card messages** with static media. Using it with multiple cards will cause the request to fail with a validation error. > GIFs and videos are not supported and will be rendered as vertical cards.
        - `orientation` 'HORIZONTAL' | 'VERTICAL': The orientation of the standalone card.
        - `image_alignment` 'LEFT' | 'RIGHT': The alignment of the image in the standalone card. This field is ignored if orientation is VERTICAL.
      - `cardWidth` 'SMALL' | 'MEDIUM': Width of each card in a carousel. <br><br> **Default:** `MEDIUM` <br> **Valid for:** Multi-card messages (2 to 10 cards). <br> **Not valid for:** Single-card messages. Setting it with one card fails validation. <br> **Platform:** Card width selection applies only on Android. For iOS, assume `MEDIUM`.
    - `to` string, required: Recipient's phone number in E.164 format.
    - `cards` RcsCardsCardsItems[], required: Collection of cards attached to the message. <br><br> **Limit:** 1 to 10
      - `buttons` RichButton[]: While buttons resemble quick replies, they remain on screen after being clicked and are card-specific. <br><br> **Limit:** 4 max
        - union
          - object: Button that opens a URL when tapped by the recipient.
            - `type` 'openUrl', required: Discriminator value: openUrl
            - `webviewMode` 'HALF' | 'TALL' | 'FULL': Controls how the URL is displayed when the button is tapped. **Default behavior:** If not specified, the URL opens in the device's default browser. If you're sending deeplinks, you should use this mode as it will open the deeplink in the native app if it is installed. **Available modes in order of size:** - `HALF` — Half-screen webview overlay - `TALL` — Tall webview overlay - `FULL` — Full-screen webview
            - `payload` string, uri, required: The URL to open when the button is tapped. Must be a valid HTTP or HTTPS URL.
            - `title` string, required: Display text for the button.
            - `metadata` string: Optional additional data to attach to this button.
          - object: Button that initiates a phone call when tapped by the recipient.
            - `type` 'call', required: Discriminator value: call
            - `metadata` string: Optional additional data to attach to this button.
            - `payload` string, required: Phone number to call in E.164 format
            - `title` string, required: Display text for the button.
          - object: Button that sends custom data back to your application when tapped by the recipient.
            - `type` 'trigger', required: Discriminator value: trigger
            - `metadata` string: Optional additional data to attach to this button.
            - `payload` string, required: Custom data sent to your webhook when the button is tapped. Use this to identify the user's choice.
            - `title` string, required: Display text for the button.
          - object: Button that prompts the recipient to share their current location.
            - `type` 'requestUserLocation', required: Discriminator value: requestUserLocation
            - `metadata` string: Optional additional data to attach to this button.
            - `title` string, required: Display text for the button.
          - object: Button that prompts the recipient to add an event to their calendar.
            - `type` 'scheduleEvent', required: Discriminator value: scheduleEvent
            - `eventDescription` string: Detailed description for the calendar event.
            - `eventEndTime` string, required: End time in ISO 8601 format.
            - `eventStartTime` string, required: Starting time in ISO 8601 format.
            - `eventTitle` string, required: Title of the event.
            - `metadata` string: Optional additional data to attach to this button.
            - `title` string, required: Display text for the button.
          - object: Button that shares a specific location with the recipient when tapped.
            - `type` 'sendLocation', required: Discriminator value: sendLocation
            - `name` string: Optional name or label for the location that will be displayed in the map app (e.g., "Central Park", "Home Office"). If not provided, the button title will be used as the location name.
            - `latLong` RichButtonDiscriminatorMappingSendLocationLatLong, required: Geographic coordinates of the location to share.
              - …
            - `title` string, required: Display text for the button.
            - `metadata` string: Optional additional data to attach to this button.
      - `media` string, url: Media file URLs to send.
      - `mediaHeight` 'SHORT' | 'MEDIUM' | 'TALL': Height of the card media. <br><br> **Default:** `MEDIUM` <br> **Valid for:** Carousel cards and vertical standalone cards. <br> **Not valid for:** Horizontal standalone cards. <br> **Requires:** The card must include a `media` field. <br> **Platform:** Media height selection applies only on Android. For iOS, assume `MEDIUM`.
      - `subtitle` string: Secondary text displayed below the title for additional context.
      - `title` string, required: Title displayed on the card.
    - `quickReplies` RichButton[]: List of interactive quick reply buttons in the message. <br><br> **Limit:** 10 max
      - union
        - object: Button that opens a URL when tapped by the recipient.
          - `type` 'openUrl', required: Discriminator value: openUrl
          - `webviewMode` 'HALF' | 'TALL' | 'FULL': Controls how the URL is displayed when the button is tapped. **Default behavior:** If not specified, the URL opens in the device's default browser. If you're sending deeplinks, you should use this mode as it will open the deeplink in the native app if it is installed. **Available modes in order of size:** - `HALF` — Half-screen webview overlay - `TALL` — Tall webview overlay - `FULL` — Full-screen webview
          - `payload` string, uri, required: The URL to open when the button is tapped. Must be a valid HTTP or HTTPS URL.
          - `title` string, required: Display text for the button.
          - `metadata` string: Optional additional data to attach to this button.
        - object: Button that initiates a phone call when tapped by the recipient.
          - `type` 'call', required: Discriminator value: call
          - `metadata` string: Optional additional data to attach to this button.
          - `payload` string, required: Phone number to call in E.164 format
          - `title` string, required: Display text for the button.
        - object: Button that sends custom data back to your application when tapped by the recipient.
          - `type` 'trigger', required: Discriminator value: trigger
          - `metadata` string: Optional additional data to attach to this button.
          - `payload` string, required: Custom data sent to your webhook when the button is tapped. Use this to identify the user's choice.
          - `title` string, required: Display text for the button.
        - object: Button that prompts the recipient to share their current location.
          - `type` 'requestUserLocation', required: Discriminator value: requestUserLocation
          - `metadata` string: Optional additional data to attach to this button.
          - `title` string, required: Display text for the button.
        - object: Button that prompts the recipient to add an event to their calendar.
          - `type` 'scheduleEvent', required: Discriminator value: scheduleEvent
          - `eventDescription` string: Detailed description for the calendar event.
          - `eventEndTime` string, required: End time in ISO 8601 format.
          - `eventStartTime` string, required: Starting time in ISO 8601 format.
          - `eventTitle` string, required: Title of the event.
          - `metadata` string: Optional additional data to attach to this button.
          - `title` string, required: Display text for the button.
        - object: Button that shares a specific location with the recipient when tapped.
          - `type` 'sendLocation', required: Discriminator value: sendLocation
          - `name` string: Optional name or label for the location that will be displayed in the map app (e.g., "Central Park", "Home Office"). If not provided, the button title will be used as the location name.
          - `latLong` RichButtonDiscriminatorMappingSendLocationLatLong, required: Geographic coordinates of the location to share.
            - `lat` number, double, required: Latitude coordinate in decimal degrees.
            - `lng` number, double, required: Longitude coordinate in decimal degrees.
          - `title` string, required: Display text for the button.
          - `metadata` string: Optional additional data to attach to this button.

## Response `200`

Successfully sent or scheduled the message.

Use our [/messages/:id](./get) endpoint to track your message.

<Accordion title="About RCS Fallback SMS Response and RCS Fallback MMS Response">
When you send an RCS message with a fallback configured, the API checks whether the recipient's phone supports RCS **before** sending. If the phone does not support RCS, the fallback SMS or MMS is sent immediately instead, and you receive one of these response types.

You will receive message statuses for the fallback message at your configured webhooks and also receive a `FALLBACK_SENT` webhook event for the original RCS message.
</Accordion>

- union
  - SendRcsResponse
    - `messageId` string, required: Unique identifier for the sent RCS message. This identifier is a string that always begins with the prefix `msg_`, for example: `msg_1234567890`.
    - `segments` integer, required: Total number of segments used across the message.
    - `totalCost` number, double, required: Total cost of sending the message.
    - `sender` string, required: Sender's phone number in E.164 format.
    - `recipient` string, required: Recipient's phone number in E.164 format.
    - `status` 'queued', required: Current status of the message.
  - ScheduledSendResponse
    - `scheduleId` string, required: Unique identifier for the scheduled send. This identifier is a string that always begins with the prefix `msg_sched_`, for example: `msg_sched_1234567890`.
    - `config` ScheduledSendResponseConfig, required: Configuration for the scheduled message.
      - `sendAt` string, required: When the message will be sent in ISO 8601 format.
      - `recurrence` string: AWS cron expression used for recurring messages.
      - `timezone` string, required: IANA timezone identifier.
      - `endDate` string: When the recurring messages stops in ISO 8601 format.
  - SendRcsFallbackSmsResponse: Returned when a fallback is configured and the recipient does not support RCS. The API checks RCS capabilities at send time. If the recipient's device doesn't support RCS, the fallback SMS is sent instead. You will also receive a `FALLBACK_SENT` webhook event for the original RCS message.
    - `messageId` string, required: Unique identifier for the sent message. This identifier is a string that always begins with the prefix `msg_`, for example: `msg_1234567890`.
    - `segments` SendSmsResponseSegments, required: Details about how the message was segmented for sending.
      - `count` number, double, required: Number of message segments used to send this message.
      - `encoding` 'gsm7' | 'utf16', required: Encoding used for the message segments.
    - `totalCost` number, double, required: Total cost of sending the message.
    - `sender` string, required: Sender's phone number in E.164 format.
    - `recipient` string, required: Recipient's phone number in E.164 format.
    - `status` 'queued', required: Message is queued for delivery.
    - `fallbackSent` true, required: Indicates that the fallback SMS was sent because the recipient does not support RCS.
    - `originalMessageId` string, required: Unique identifier of the original RCS message that triggered this fallback. Always begins with the prefix `msg_`. This is the RCS message that could not be delivered — the `messageId` field on this response refers to the actual SMS that was sent as the fallback.
  - SendRcsFallbackMmsResponse: Returned when a fallback is configured and the recipient does not support RCS. The API checks RCS capabilities at send time. If the recipient's device doesn't support RCS, the fallback MMS is sent instead. You will also receive a `FALLBACK_SENT` webhook event for the original RCS message.
    - `messageIds` string[], required: Array of unique message identifiers for an individual MMS send. Each identifier is a string that always begins with the prefix `msg_`, for example: `msg_1234567890`. <br><br> When media assets are too large to fit in a single MMS and `options.multiple_messages` is set to true, the content is automatically split across multiple messages. Each split message gets its own ID, and all IDs are returned in this array. <br><br> Note: When sending to audiences, you'll receive multiple response objects (one per recipient), each containing its own messageIds array.
    - `segments` number, double, required: Total number of segments used across the message.
    - `totalCost` number, double, required: Total cost of sending the message.
    - `sender` string, required: Sender's phone number in E.164 format.
    - `recipient` string, required: Recipient's phone number in E.164 format.
    - `status` 'queued', required: Message is queued for delivery.
    - `fallbackSent` true, required: Indicates that the fallback MMS was sent because the recipient does not support RCS.
    - `originalMessageId` string, required: Unique identifier of the original RCS message that triggered this fallback. Always begins with the prefix `msg_`. This is the RCS message that could not be delivered — the `messageIds` field on this response refers to the actual MMS message(s) that were sent as the fallback.

## Other responses

- `400`: The request was unacceptable, often due to providing an invalid update. <br> Errors may originate from invalid payload or from Pinnacle's additional validation checks. For example, providing an URL that cannot be accessed, updating a campaign that is currently being reviewed, updating data that you cannot access, sending a malformed message, and so on. <br> For `Pinnacle Validation Error` inspect the `error` payload to determine the source of the failure. These errors are likely due to additional validation and business logic checks.<br> For `Request Validation Error` inspect the `description` and `errors` payload to determine the source of failure. These errors are likely due to invalid payload inside the request.
- `401`: The request lacks valid authentication credentials or the provided credentials are invalid. <br> Ensure you're including a valid API key in the request headers and that your account has the necessary permissions to access this endpoint.
- `402`: Insufficient credits to complete this request. <br> This occurs when your account balance is below the required amount for processing the operation. Please add credits to your account to continue using the service.
- `403`: Your subscription does not include access to this feature. <br> This occurs when attempting to use functionality that requires a higher subscription tier. Please upgrade your subscription to access this feature.
- `404`: The requested resource could not be found. <br> This may occur if the identifier is incorrect, the resource has been deleted, or you don't have permission to access it.
- `500`: An unexpected error occurred on Pinnacle's servers while processing your request. <br> If this error persists, please contact support with the request details.
- `501`: The requested functionality is not implemented on the server. <br> This typically indicates that the feature or endpoint you attempted to access is unavailable or not yet supported.

---

[API](https://skmtc.dev/pinnacle/apis/pinnacle-2.md) - [All operations](https://skmtc.dev/pinnacle/apis/pinnacle-2/llms.txt) - [OpenAPI document](https://skmtc.dev/pinnacle/apis/pinnacle-2/revisions/45416dadab79?raw)