What FlashAPI does and who it is for
FlashAPI is an independent REST API that gives developers structured access to publicly visible Instagram data — the kind of information a logged-in browser session can already see, but delivered in clean JSON without screen-scraping or manual browsing. The target audience is analytics engineers, dashboard builders, CRM integrators, and market researchers who need reliable, programmatic reads on Instagram public profiles and content.
The API is explicit about its scope: it only returns data from public accounts, it does not support interaction automation (likes, follows), and it makes no claim to offer any access to private or restricted content. It is also independent of Meta — not affiliated, endorsed, or officially connected.
Endpoint coverage
FlashAPI exposes 34 usable endpoints organised into five functional groups.
User data (19 endpoints)
This is the largest group and covers most of what an analytics tool needs. You can fetch a user's numeric ID from a username (/ig/user_id/), then pull full profile objects in several flavours: by user ID (/ig/info/), by username (/ig/info_username/), as a business profile variant (/ig/business/), or via two additional web-profile information endpoints (/ig/web_profile_info/, /ig/additional_info/). The multiplicity here is typical of Instagram data APIs where different internal endpoints on the platform return slightly different field sets — useful when one response is missing a field you need.
Beyond profile metadata, you can retrieve follower and following lists (/ig/followers/, /ig/following/), feed posts and reels — each available by user ID or username — and stories (both by user and by story ID). Highlights are also covered with a tray endpoint and a per-highlight detail endpoint. Rounding out this group are username suggestions, similar accounts, and an engagement summary that calculates account engagement based on the last 12 posts (/ig/basic_engagement/).
Media info (5 endpoints)
Given a media shortcode or ID, you can pull post metadata in two detail levels (/ig/post_info/, /ig/post_info_v2/), the list of likes (/ig/likes/), top-level comments (/ig/comments/), and nested child comments (/ig/child_comments/). This group is where most content analytics work happens — pulling engagement numbers, reading caption text, or paginating through comments for sentiment analysis.
Music (2 endpoints)
Two endpoints handle Instagram's audio layer: a search endpoint (/ig/music_search/) that returns track information and a download URL, and a trending music endpoint (/ig/music_trending/). Useful if you are building a trend-tracking tool focused on audio content.
Location (2 endpoints)
You can search for a location to resolve its ID (/ig/location_search/) and then retrieve public media tagged at that location (/ig/locations/). Practical for geo-focused content monitoring or local business analytics.
Other (5 endpoints)
This catch-all group includes user guides (/ig/guides/), tagged posts (/ig/tagged/), user search (/ig/search/), hashtag search (/ig/hashtag/), and preliminary hashtag data (/ig/preliminary_hashtag/). The hashtag endpoints are particularly relevant for brand monitoring and campaign tracking.
Pricing
FlashAPI uses a freemium billing model with four tiers.
| Plan | Price | Requests/month | Rate limit |
|---|---|---|---|
| BASIC | $0 | 30 | — |
| PRO | $9.90 | 10,000 | 1 req/second |
| ULTRA | $27.90 | 50,000 | 100 req/minute |
| MEGA | $75.90 | 150,000 | 125 req/minute |
The MEGA plan is marked as recommended and includes overage billing at $0.0006 per request beyond the 150,000 monthly cap, which works out to $0.60 per additional thousand requests.
The BASIC tier's 30 requests per month is effectively a testing allowance — enough to validate response shapes and write integration code, but not enough to run any meaningful production workload. PRO at $9.90 suits individuals or small tools doing light monitoring. At 10,000 requests across a 30-day month, that is roughly 330 calls per day, which covers a moderate number of profile checks or post lookups at a comfortable pace given the 1 request/second limit. ULTRA and MEGA are for production analytics platforms where you're polling many accounts or media objects frequently.
Note that ULTRA (100 req/min) and MEGA (125 req/min) have similar rate limits despite a significant price difference — the main variable between them is the monthly request ceiling and the presence of overage billing on MEGA.
Practical use cases
- Influencer analytics platforms — automate the retrieval of follower counts, engagement rates, and content cadence for a roster of public accounts without manual lookups.
- Brand monitoring — combine the hashtag search and tagged post endpoints to track brand mentions and user-generated content.
- Competitive benchmarking — pull profile data and post metrics for a set of competitor accounts and feed them into a BI dashboard.
- CRM enrichment — append Instagram profile data to contact records for accounts where users have provided their public handle.
- Trend tracking — use the trending music and preliminary hashtag endpoints to surface rising content patterns.
Latency and reliability
The reported average latency of 2,081 ms is worth taking seriously in your architecture decisions. Responses are averaging just over two seconds, which means FlashAPI calls should not sit in any synchronous user-facing path. Instead, design your integration to fetch data asynchronously — background jobs, scheduled workers, or queue-backed pipelines — and cache results appropriately. The 99% average success rate and the provider-reported 99.97% uptime suggest that the occasional slow call is the primary reliability concern rather than outright failures.
Limitations and things to check before integrating
Public data only. The API explicitly does not return data from private profiles. Any use case that requires follower-list traversal into non-public accounts will not work.
Platform policy exposure. FlashAPI collects from publicly accessible sources, but Instagram's terms restrict automated data collection. Developers are responsible for ensuring their specific use case complies with applicable laws and the platform's policies before going to production.
No write or interaction endpoints. This is strictly a read API. Automated likes, follows, DMs, or any other interaction are not supported and are explicitly prohibited.
Low free tier ceiling. Thirty requests on the free plan is enough to explore the API but essentially nothing for evaluation at scale. Budget for at least the PRO plan when load-testing your integration.
Overage only on MEGA. If you are on ULTRA and exceed 50,000 requests, you will need to upgrade rather than rely on overage billing. Plan accordingly if your usage is variable.
Getting started
Authentication uses an API key generated after registering on the provider's website. All major languages are supported since the API is standard REST returning JSON — Python, JavaScript, PHP, Java, and any HTTP client will work. Usage limits and current consumption are visible in the account dashboard. Technical support is available via Telegram at the channels listed in the documentation (@ig_api and @api_profi). Subscriptions can be cancelled at any time from account settings.
