Telegram API

Read-only Telegram API for clean JSON.

Connect a Telegram account slot and call tenant-scoped GET endpoints for Telegram data available to the connected account, including chats and channels it has joined but does not own. dataz.md is not the Telegram Bot API and does not send messages or change Telegram state.

Get started Explore docs

Supported Telegram surfaces

Keep endpoint claims limited to the verified read-only categories available in the current API.

Chats and channels

Chats, channels, channel logs, chat messages, and channel messages visible to the connected account.

People and DMs

Contacts, existing friends, direct-message lists, direct-message history, and members.

Discussion structure

Forum topics and topic messages for chats and channels where the account has access.

Example GET calls

The tenant gateway route includes the workspace slug and account slug; the provider is inferred from the account.

GET /v1/{tenant_slug}/accounts/{account_slug}/chats
GET /v1/{tenant_slug}/accounts/{account_slug}/channels/{channel_id}/messages
GET /v1/{tenant_slug}/accounts/{account_slug}/contacts
GET /v1/{tenant_slug}/accounts/{account_slug}/topics/{chat_id}/{topic_id}/messages

Read-only boundaries

No sending, editing, deleting, reacting, joining, or changing contacts.
No moderation actions, bot commands, webhook workflows, setup/token routes, or provider-account control routes.
Use Authorization: Bearer <key> or X-API-Key with tenant gateway calls.

How a request flows

Calls hit a tenant-scoped gateway, which reads through the connected account and returns plain JSON. Nothing in the path can write to Telegram.

Your app calls the tenant gateway with an API key, the gateway reads through the connected Telegram account, and the response comes back as JSON.

Sample response

GET /v1/{tenant_slug}/accounts/{account_slug}/chats

[
  {
    "id": "-1001234567890",
    "name": "Example channel",
    "type": "channel",
    "username": "example_channel",
    "unread_count": 0
  },
  {
    "id": "-1009876543210",
    "name": "Second example group",
    "type": "group",
    "username": null,
    "unread_count": 3
  }
]

Pagination and rate limits

List endpoints take a limit query parameter. Chat listings default to 100 with a ceiling of 500; chat messages default to 50 with a ceiling of 100; member reads default to 100 with a ceiling of 1000.
Telegram flood-wait responses become HTTP 429 with code: "provider_rate_limited", retryable: true, and retry_after_seconds, plus a Retry-After header.
Error responses carry X-Request-ID and X-Dataz-Request-ID for support correlation.
Exact defaults and bounds for every endpoint are published on the crawlable Telegram reference.

Build against the Telegram API surface.

Open the Telegram docs for endpoint details, or create a workspace and activate an account slot.

Open Telegram docs Crawlable Telegram reference Telegram OpenAPI Run the quickstart Get started

Last updated August 24, 2026