Fetch specific stories by id
Specific stories of a peer by id. ids is a comma-separated list of story ids (for example 1,2,3), and the answer carries count plus the matching story objects with caption, entities, date and media. Ids are permanent: a request for 1,2,3 on channel id 1006503122 returned count: 3 including a story posted 3 December 2023, so archived stories remain readable long after the 24-hour window in which they are "active" (measured 16 September 2026). An id nobody posted answers 200 with count: 0 and stories: null; a list that cannot be parsed answers 400 INVALID_REQUEST. Story media file references are downloadable via GET /v1/files/{file_id}. Resolve a @username with /v1/usernames/{username} first to get the numeric peer_id.
Request
- Base URL: https://telegram155.p.rapidapi.com
- URL: https://telegram155.p.rapidapi.com/v1/peers/{peer_id}/stories/{ids}
- Auth: none declared
Path parameters
Numeric Telegram peer id (channel or user). Obtain from /v1/usernames/{username}, /v1/phones/{phone}, /v1/contacts/search, or any prior response's peer.user_id / peer.channel_id field.
Comma-separated list of story ids (e.g. 42,41). Maximum 100.
Response
Requested stories.
Changes
No recorded changes to this operation across all 1 revision of this API.