Instagram API The issue with the API was fixed!

Channel
RapidApi TikTok/Instagram/Amazon/Target API
@logicApi
On this record: Growth · Engagement · Posts · Cite this entry
302subscribers
-4 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1001431140853 |
|---|---|
| Type | Channel |
| Username | @logicApi |
| Created | Between 1 April 2019 and 27 September 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 24 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 24 August 2026 |
| On Telegram | t.me/logicApi |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 24 Aug 2026, 08:53 | 302 | -3 |
| 8 Aug 2026, 21:32 | 305 | -1 |
| 8 Aug 2026, 07:49 | 306 | no change |
| 7 Aug 2026, 21:54 | 306 | first reading |
Engagement
20 posts held, back to 27 September 2021 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 6 March 2024. An engagement rate over an empty window would be a number about nothing.
Recent posts
Instagram API There is an issue with the API, currenlty working on a solution!
New endpoints in Instagram API - /hashtag/feed/reels - hashtag reels feed - /location/search - get locations metadata by using location name - /location/stories - get location user stories by using set of locations IDs
TikTok API All issues related to the api were fixed
New endpoints in Instagram API - /user/tagged/feed - user tagged feed, post where user was tagged - /user/guides/feed - user guides feed
New endpoints in Instagram API - /user/feed/v2 - returns more data related to user feed - /hashtage/feed/v2 - returns more data related to hashtag feed - /hashtag/info - return hashtag metadata such as top, recent posts and etc
Amazon API The issue with the api was resolved
Instagram API The api experienced issue for the past few hours, everything was resolved and api is stable again
TikTok API - issue Below endpoints started experiencing issues. Currently we are working on a solution - /live/user/feed - /live/user/feed/v2
Instagram Api Below endpoints can retrieve data by using user_id or username. By using user_id your request will be executed x2 faster - /user/feed - /followers - /followings - /user/contacts - /user/stories - /user/reels - /user/highlight/reels
TikTok Api The issue with the following endpoints was fixed - /live/music/feed
TikTok Api The issue with the following endpoints was fixed - /live/hashtag/feed - /live/hashtag/search - /live/user/search
Showing the 12 most recent of 20 posts we hold for @logicApi. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked ≈ was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.
Cite this entry
A live page changes as we take new readings, so a citation should name the measurement it is based on, not just the URL. The line below cites the subscriber count as measured 24 August 2026 — this entry's latest reading, not the date you are reading this.
“RapidApi TikTok/Instagram/Amazon/Target API” (@logicApi), 302 subscribers as measured 24 August 2026. Telegram Register, tgregister.com/channel/logicApi.
Full measurement history, CC BY 4.0. Every reading this register holds for this entry, not just the latest one, as a dated, downloadable record: CSV · JSON. Free to use with attribution to tgregister.com. Each file carries its own generation timestamp, which is the figure to cite for exactly when the data was retrieved.