---
# @generated by sylphx-gen 0.1.0 from contracts@e145cc7cf1bc9605f2b27439e5e17ed76a1a2fd7e7021906a013f7565e4a0cd5. Do not edit.
title: "sylphx events realtime_messages"
description: "The sylphx events realtime_messages commands of Sylphx Events: every verb, with its argument, its flags and a run line."
type: reference
product: realtime
summary: "Every sylphx events realtime_messages command: its argument, its flags and a run line."
updated: 2026-09-28
nav: false
---

The `realtime_messages` commands of Sylphx Events, as the CLI spells them: the same
calls as [the `realtime_messages` API page](/docs/api/realtime_messages), typed for the
shell. [Install, sign in and the grammar](/docs/cli) are on the CLI index.

## get

Gets one retained message of a channel.

**`NAME`** — the resource's name; a bare id is enough below the linked
project.

**CLI**

```bash
sylphx events realtime-messages get orgs/acme/projects/shop/envs/production/realtime_channels/realtime-channel/realtime_messages/realtime-message
```

`GET https://api.sylphx.com/v1/orgs/acme/projects/shop/envs/production/realtime_channels/realtime-channel/realtime_messages/realtime-message` · scope `events:read` · effect `read` · [Request, response and examples](/docs/api/realtime_messages/get)

## list

Lists a channel's retained messages, oldest first.

**`PARENT`** — optional: the CLI fills it from the linked project or the
key's scope when it is left out.

**CLI**

```bash
sylphx events realtime-messages list orgs/acme/projects/shop/envs/production/realtime_channels/realtime-channel
```

`GET https://api.sylphx.com/v1/orgs/acme/projects/shop/envs/production/realtime_channels/realtime-channel/realtime_messages` · scope `events:read` · effect `read` · [Request, response and examples](/docs/api/realtime_messages/list)

**Flags**

| Flag | Type | What it does |
| --- | --- | --- |
| `--page-size` | `int` | At most this many; default 50, clamped to 1000. |
| `--page-token` | `string` | `next_page_token` of the previous page. |
| `--filter` | `string` | Empty, or `sequence > N` to start after message N (resume). |