List Telegram bot subscribers
Lists users who started this bot. Each item includes a ready conversationContext for POST /api/v2/messages/send with channel=telegram_bot.
When to use it. To copy the numeric chatId before channel=telegram_bot.
Code example
Correct: Bot subscribers
curl --location 'https://raselsms.com/api/v2/telegram-bots/64f1a2b3c4d5e6f7a8b9c0d1/subscribers' \--header 'X-API-Key: YOUR_API_KEY'Incorrect: Incorrect: bot you do not own
curl --location 'https://raselsms.com/api/v2/telegram-bots/000000000000000000000000/subscribers' \--header 'X-API-Key: YOUR_API_KEY'You cannot list subscribers of another account's bot.
Response example
200 — Bot subscribers
{ "success": true, "data": { "accountId": "64f1a2b3c4d5e6f7a8b9c0d1", "subscribers": [ { "accountId": "64f1a2b3c4d5e6f7a8b9c0d1", "chatId": "123456789", "telegramUserId": "123456789", "username": "customer", "firstName": "Ali", "lastName": null, "lastSeenAt": "2026-08-31T12:00:00.000Z", "conversationKey": "telegram_bot:64f1a2b3c4d5e6f7a8b9c0d1:123456789", "conversationContext": { "moduleType": "telegram_bot", "accountId": "64f1a2b3c4d5e6f7a8b9c0d1", "chatId": "123456789" } } ], "page": 1, "limit": 20, "total": 1, "hasMore": false }}404 — Incorrect: bot you do not own
{ "success": false, "code": "NOT_FOUND", "error": "Bot not found"}You cannot list subscribers of another account's bot.
401 — Invalid API key.
{ "success": false, "requestId": "msgreq_1739012345678_abc123", "code": "UNAUTHORIZED", "error": "Missing or invalid API key"}HTTP request
GET /api/v2/telegram-bots/{botId}/subscribers
Request Headers
| Header | Type | Description |
|---|---|---|
| X-API-Key | string | Your Rasel API key. Send it on every documented request except inbound webhooks. * |
Path parameters
| Field | Type | Description |
|---|---|---|
| botId | string | Telegram bot Mongo id from GET /api/v2/telegram-bots (same as accountId). * |
Query parameters
| Field | Type | Description |
|---|---|---|
| q | string | Optional search on chatId, username, or name. |
| page | integer | 1-based page number. Default 1. |
| limit | integer | Page size. Typical range is 1-50 for conversation context and 1-500 for account lists. |
Response Fields
| Field | Type | Description | Example |
|---|---|---|---|
| success | boolean | True when the operation succeeded, or when at least one batch recipient succeeded. | |
| data | json | Primary payload for list and snapshot endpoints. |
Status Codes
| Status | Description |
|---|---|
| 200 | Success. |
| 400 | Invalid request, validation error, or the resource cannot be used in this state. |
| 401 | Missing or invalid API key. |
| 403 | Phone not verified, missing permission, or the account cannot perform this action. |
| 404 | Resource not found for this API key owner. |
| 429 | Rate limit exceeded, or the maximum number of verification attempts was reached. |
Try it
Parameters
Telegram bot Mongo id from GET /api/v2/telegram-bots (same as accountId).
Optional search on chatId, username, or name.
1-based page number. Default 1.
Page size. Typical range is 1-50 for conversation context and 1-500 for account lists.
Request
GET /api/v2/telegram-bots//subscribersResponse
Send a request to see the response.