RCS

Send an RCS message

Changed on

Queues an outbound RCS message through the selected RCS agent. Check recipient capabilities before sending features that require RCS support.

post/messages/rcs

Request

  • Base URL: https://api.telnyx.com/v2
  • URL: https://api.telnyx.com/v2/messages/rcs
  • Auth: HTTP bearer

Headers

Idempotency-Keystring

Optional opaque, unquoted key for safely retrying the same logical request. Keys must contain 1 to 255 letters, numbers, hyphens, or underscores. Generate a unique UUID v4 for each operation and reuse it only when retrying that operation with the same request. Invalid headers—including duplicate, empty, malformed, or overlong values—return 400 with error code 10015. A request already in progress with the same key returns 409; reusing the key with a different request returns 422. Only successful responses are replayed, for up to 24 hours. Do not include sensitive data in the key.

Request body

agent_idstring required

RCS Agent ID

tostring required

Phone number in +E.164 format

messaging_profile_idstring required

A valid messaging profile ID

type'RCS'

Message type - must be set to "RCS"

webhook_urlstring url

The URL where webhooks related to this message will be sent.

Response

Successful operation

Changes

  • 90422ac0fcf5Revision changes
    • info

      added the new optional header request parameter Idempotency-Key

    • info

      added the non-success response with the status

    • info

      added the non-success response with the status

    • info

      added the non-success response with the status

  • 1571b0380bd7Revision changes
    • breaking

      the response's body type changed from object to no type for status

    • breaking

      the / response's property type changed from object to no type for status

    • breaking

      the // response's property type changed from integer to string, and format from int32 to no format for status