---
title: "View scheduled messages"
locale: en
url: https://tlg.builera.app/en/docs/reference/rest/messages.list_scheduled
verified: 2026-10-24
app_version: "2.0"
generated: true
---

# View scheduled messages

Read the chat's scheduled messages from Telegram (id, send time, text). Follow the operation for the list.

Read the chat's scheduled messages from Telegram (id, send time, text). Follow the operation for the list.

## Overview

| Name | Value |
| --- | --- |
| Code | `messages.list_scheduled` |
| Scope needed | `messages.read` |
| Risk | Read |
| May need confirmation | No |
| Runs as | Queues work for a node |
| Needs `Idempotency-Key` | No |
| Member roles allowed | `owner`, `manager`, `agent` |
| Needs a worker from version | `1.0.19` |
| In the app | Inbox → chat menu → Scheduled messages |

## Input fields

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `conversationId` | `uuid` | Yes |   |

## Example request

```bash
curl -X POST https://tlg.builera.app/api/public/v2/ops/messages.list_scheduled \
  -H "Authorization: Bearer $TELEGRAM_AUTO_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"conversationId":"00000000-0000-0000-0000-000000000000"}'
```

## Output fields (`data`)

| Field | Type | Required |
| --- | --- | --- |
| `ok` | `true` | Yes |
| `jobId` | `text` | Yes |

## Example answer

```json
{
  "data": {
    "ok": true,
    "jobId": "00000000-0000-4000-8000-000000000000"
  }
}
```

## Using it over MCP

Not listed on any profile: call `tools_describe` then `tools_run` with `code: "messages.list_scheduled"`. Tool name when listed: `messages_list_scheduled`.