---
title: "Get RCS message"
method: GET
path: "/v2/rcs/messages/{id}"
tags: ["RCS"]
---

# Get RCS message

`GET /v2/rcs/messages/{id}`

Retrieves details of a previously sent RCS message by its unique identifier.
Returns message content, delivery status, and metadata.

## Path parameters

- `id` string, uuid, required

## Response `200`

OK

- object
  - `data` object, required — Success response payload
    - `id` string, required — Unique identifier for the message.
    - `account_id` string, required — Account identifier that sent the message.
    - `message_ref` string — Optional reference ID set by the user for the message.
    - `sender` string, required — Registered RCS Agent ID.
    - `recipient` string, required — Recipient phone number in international format.
    - `content_type` 'text', required — Type of the message content.
    - `content` object, required — Content of the message.
      - `text` RCSText, required — Text content for the message.
        - `message` string, required — The text message body. **Message Types:** - **Basic RCS Messages**: Up to 160 characters (SMS format in RCS) - **Simple RCS Messages**: Up to 3072 characters with emoji and UTF-8 support
    - `sms_fallback` RCSSMSFallback — Provides intelligent fallback for non-RCS capable devices and carrier delivery issues. If the RCS message fails, the SMS will send the configured message to the recipient instead.
      - `sender` string — The sender number to use for SMS fallback, which can be in [E.164](http://en.wikipedia.org/wiki/E.164) international format or an alphanumeric sender ID.
      - `message` string, required — The message to send through SMS. SMS messages are subject to certain character limitations, please read our SMS documentation for details.
    - `created_at` string, date-time, required — Timestamp in RFC3339 format (e.g., 2025-08-26T10:30:00Z) when the message was created on the server.
    - `status` 'QUEUED' | 'SENT' | 'DELIVERED' | 'READ' | 'FAILED', required — Current status of an RCS message.
    - `events` RCSMessageEvent[] — Array of lifecycle events for the message.
      - `event_type` 'SENT' | 'DELIVERED' | 'READ' | 'FAILED', required — Type of event: one of `SENT`, `DELIVERED`, `READ`, `FAILED`.
      - `created_at` string, date-time, required — Timestamp in RFC3339 format (e.g., 2025-08-26T10:30:00Z) when the event occurred.
      - `details` string, required — Description of the event.
  - `request` object — Optional metadata (e.g. requestId, traceId)
  - `meta` object — Optional pagination, feature flags, etc.

## Other responses

- `401` — Unauthorized
- `404` — Not Found
- `500` — Internal Server Error

---

[API](https://skmtc.net/kudosity/apis/transmit-message-api.md) · [All operations](https://skmtc.net/kudosity/apis/transmit-message-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/kudosity/transmit-message-api/versions/bf132756e067/schema)