Documentation

Keys are issued and billed by RapidAPI. Every request carries two headers and nothing else — no phone number, no api_id, no session file.

x-rapidapi-key: YOUR_KEY
x-rapidapi-host: telegram155.p.rapidapi.com

Three full calls with the responses they return are on the quickstart page, and four things worth building on them are in the cookbook.

The machine-readable version of this table — parameters, response shapes and worked examples — is /openapi.json, OpenAPI 3.1.

The same specification also ships as a Postman collection: /tgatlas.postman_collection.json. In Postman pick Import, paste that link, and all 19 requests arrive grouped by subject with both RapidAPI headers already in place and the path parameters pre-filled from the examples, so the only empty field left is your key.

History and replies use Telegram’s own cursor scheme: offset_id, add_offset, max_id, min_id. Pass the id of the oldest message you received as offset_id to get the page before it. History responses also carry next_page, which does the same walk without any bookkeeping on your side.

Member lists. Telegram hides the member list of a broadcast channel from everyone who is not an admin — that is the platform, not the API. full_chat.can_view_participants on /v1/channels/{peer_id} tells you in advance which way the participants call will go, and groups with an open list answer it in full.

Comment threads. A post has a thread when it has comments: every message in /v1/peers/{peer_id}/history carries replies.comments, and full_chat.linked_chat_id tells you whether the channel has a discussion group at all. Check either one and the replies and discussion calls land every time.

Every non-2xx response arrives in one envelope, so a single error path covers the whole API:

{ "error": "service temporarily unavailable", "code": "SERVICE_UNAVAILABLE", "hint": "retry shortly" }

error is for your logs, code is for your code, and hint appears wherever there is a concrete next step. There are seven codes and the list does not grow quietly:

Three budgets are metered independently, and every response reports what is left of each one: monthly requests, discovery lookups and phone resolution. Only four paths spend a lookup: /v1/usernames/{username}, /v1/contacts/search, /v1/messages/search and /v1/channels/recommendations. Reading a channel and walking its history draws on requests alone. Resolving a run of handles back to back is the sequence that moves the lookup counter, and x-ratelimit-lookups-remaining shows the room you have before it does.