# Best Instagram Scraper: Six Ways to Get Instagram Data, Priced per 1,000 Rows

> Best Instagram scraper, tested Nov 15: per 1,000 posts Apify costs $1.50+, Bright Data $1.50, TikHub from $0.02, EveryInfra $0.003 to $0.011.

- Canonical page: https://everyinfra.com/en/blog/best-instagram-scraper
- Published: 2026-11-15T02:06:00+08:00 · Fact-checked: 2026-11-15T01:30:00+08:00

For 1,000 public Instagram posts, the Apify Instagram Scraper lists $1.50 (Business tier) to $2.70 (Free tier). Bright Data lists $1.50 pay as you go. TikHub charges $0.001 per request, which is about $0.083 at the default page of 12 posts and $0.020 with `count` at its maximum of 50. On November 15, 2026, we called the EveryInfra `instagram/user_posts` capability twice at $0.000556 per call. One call returned 200 posts for natgeo and one returned 50 posts for bluebottle. That is $0.00278 and $0.0111 per 1,000 posts.

The gap is large only for data that comes back many rows per request. It is several hundred times against the per-row providers and 1.8 to 30 times against TikHub. Profiles are billed one by one everywhere. For 1,000 profiles we measured $0.556, TikHub lists $1.00, Bright Data lists $1.50, and Apify lists $1.60 to $2.60. So on profiles the difference shrinks to 1.8 to 4.7 times.

The Meta Graph API has no per-call fee, but it reads only business and creator accounts and needs app review. Open-source libraries are free too. But instaloader got 14 new issues in 30 days, with 429 rate limits, broken logins and a broken Reels listing.

> **Key points**
>
> - Posts: per 1,000 posts, Apify costs $1.50 to $2.70 and Bright Data $1.50. TikHub costs $0.020 to $0.083 (50 or 12 per page), and EveryInfra measured $0.00278 to $0.0111.
> - Profiles: per 1,000 profiles, we measured $0.556, against $1.00 at TikHub, $1.50 at Bright Data and $1.60 to $2.60 at Apify.
> - The `limit` value is a ceiling, because comments returned 15 of 100 rows and a hashtag returned 30 of 100.
> - EveryInfra and Bright Data do not bill failures, Apify bills only results, and TikHub bills every HTTP 200.
> - Our 12 live calls cost $0.006433, and the 4 failed calls cost nothing.

Every "per 1,000" number in this ranking uses one formula. Take the USD that one request actually charged. Divide it by the rows that request actually returned. Multiply by 1,000. Prices for other providers come from their public pricing pages, Store pages and public APIs, read on November 15.

Our prices come from `charged_usd` in each live response on the same night. The providers bill in different units. Apify and Bright Data bill per result row. TikHub and EveryInfra bill per request. A shared denominator is the only fair way to put them in one table. We use rows actually returned, so a short response makes our price look worse, never better.

![Scatter chart of USD per 1,000 results on a log scale from $0.001 to $10. Four rows: Profiles, Comments, Reels, Posts. Gray marks for Apify Free, Apify Business and Bright Data pay as you go sit between $1.00 and $2.70. TikHub has two points each on Reels and Posts, about $0.083 at the default 12 per page and $0.020 at the maximum 50 per page, and one at $1.00 on Profiles. Teal EveryInfra points: two on Posts at $0.00278 and $0.0111, Reels at $0.0119, Comments at $0.0528 and Profiles at $0.556.](https://everyinfra.com/articles/best-instagram-scraper/fig-01-per1k-scatter.en.light.svg)

On October 26 we compared Apify alone with EveryInfra in 26 live calls, in the [Apify Instagram Scraper alternative](/en/blog/apify-instagram-scraper-alternative). The code steps are in the [Python guide to Instagram posts and comments](/en/blog/scrape-instagram-posts-comments-python). For the six approaches here, all prices and calls are new reads from November 15.

## Best Instagram scraper ranking: six approaches in one table

| Approach | Billing unit | 1,000 posts | 1,000 profiles | Failed or empty results | Entry cost | Steps to first data | MCP for AI tools |
| --- | --- | --- | --- | --- | --- | --- | --- |
| Meta Graph API (Business Discovery) | No per-call fee, rate limited | $0 | $0 | Not applicable | Free, needs a professional account and app review | 7 steps, 2 of them wait for review | Not found |
| Open source (instaloader, instagrapi) | Free | $0 | $0 | Not applicable | Free, bring your own IPs and accounts | 3 to 4 steps | Not applicable |
| Apify Instagram Scraper | Per result | $1.50 to $2.70 | $1.60 to $2.60 | No results, no result fee | Free plan gives $5 a month | 5 steps (their own tutorial) | Not checked in the pages we read |
| Bright Data Instagram Scraper API | Per record | $1.50 (pay as you go) | $1.50 (pay as you go) | Failed deliveries are free | 5,000 free records a month | 4 steps, 1 to 3 minutes per job | MCP listed in README |
| TikHub | Per request | $0.020 to $0.083 (50 or 12 per page) | $1.00 | Every HTTP 200 is billed | $5 minimum top-up | 4 to 5 steps (the v1 post endpoint needs a user_id first) | MCP listed in FAQ |
| EveryInfra `instagram/*` | Per request | $0.00278 to $0.0111 (measured) | $0.556 (measured) | Not billed, empty results refunded | $1 trial credit, no monthly fee | 4 to 5 steps | Remote MCP |

We read the other prices between 00:33 and 01:10 Singapore time on November 15. The Apify column covers the Instagram Scraper and the Instagram Profile Scraper from the Free tier to the Business tier. Higher Platinum and Diamond tiers exist for enterprise customers. The Bright Data column is the pay-as-you-go rate. Its Scale plan includes 384,000 records and charges $1.30 per 1,000 above that. Our column holds live results from that night, and the two post numbers come from two different accounts.

For posts, Reels and comments in bulk, the per-request providers are 10 to 1,000 times cheaper than the per-row providers. TikHub and EveryInfra bill per request. Apify and Bright Data bill per row. For profiles looked up one by one, all five paid options fall between $0.50 and $2.60 per 1,000.

Meta and open source cost nothing per call. You pay with review time, accounts, IP addresses and maintenance instead.

Per-row and per-request billing react in opposite ways to how often an account posts. natgeo posted 200 times in 67 days, about three posts a day. bluebottle posted 50 times in 139 days, about one post every 2.8 days. With per-row billing, a month of natgeo costs about 90 rows and a month of bluebottle about 11 rows. Quiet accounts are cheap.

With per-request billing, every check costs the same, so you set the interval by posting rate. Check natgeo once a day for 30 posts. Check bluebottle once a week. With that schedule, 100 slow accounts need about 430 requests a month, which is $0.24.

## How we compared: price, fields and setup steps

Two rules complete the price formula. First, provider prices are the unit prices on their public pages, without monthly fees. Monthly fees appear later in the "Three monthly bills" section.

Second, the TikHub post price uses the `count` parameter of the v1 `fetch_user_posts` entry in its OpenAPI file. The default is 12 and the maximum is 50, so we show a range. Its comment endpoint does not state a page size, so we leave that cell empty. Every EveryInfra price traces back to one live call. We record the time to the second, copy `charged_usd` from the response and recompute the division with a script.

Fields have two layers. The first layer is what the documentation lists. Bright Data lists 26 output fields for profiles, 40 for posts, 27 for Reels and 14 for comments. Our catalog `response_fields` lists 19, 21, 22 and 11.

The second layer is fields with a value in at least one returned row. Only our own data can show that layer, because we only called our own API. The two layers together show the distance between "documented" and "delivered". For example, all 200 posts from `user_posts` had an empty `view_count`, while all 100 Reels had a `play_count`.

Setup steps count from "nothing" to "first JSON file". Creating an account is one step. Getting a key is one step. A top-up is one step. Looking up an intermediate ID, such as the user_id that the TikHub v1 post endpoint needs, is one step.

Sending the request is one step. Polling an async job adds one more. Meta adds an app, a linked professional account, permission requests and two reviews. We counted from each provider's own docs and tutorials. We did not create accounts with the other providers.

| Approach | Step 1 | Step 2 | Step 3 | Step 4 | Step 5 and later |
| --- | --- | --- | --- | --- | --- |
| Meta Graph API | Create a Meta developer app | Prepare an Instagram professional account (Facebook Login also needs a Page) | Request `instagram_basic` and two other permissions | App Review | Business Verification, find your IG user ID, send `business_discovery` |
| instaloader | Install Python | `pip install instaloader` | Run it with a profile name | Log in or change IP when rate limited | — |
| Apify | Find Instagram Scraper in the Store | Click Try for free | Enter a profile URL or search term | Adjust the input | Start the run and export |
| Bright Data | Sign up (no card) | Get an API token | `pip install brightdata-sdk` | Run the script and wait 1 to 3 minutes | — |
| TikHub | Sign up | Top up $5 (only 8 of 157 Instagram endpoints accept free credit) | Get a key | For the v1 endpoint, look up the user_id by username; the v2, v3 and web_app post endpoints take a username | Fetch the posts |
| EveryInfra | Sign up | Claim the $1 trial or top up | Create a key | `POST /api/v1/social` with the plain `username` | Poll `poll_url` for the post list |

## Meta Graph API: free, but only for professional accounts

The [Instagram Platform overview](https://developers.facebook.com/docs/instagram-platform/overview) was updated on October 29, 2026. It describes three setups. Unified Login is the recommended setup for new integrations. Instagram Login and Facebook Login are the other two, and Facebook Login needs a linked Facebook Page. All three serve Instagram professional accounts, which means business and creator accounts.

The overview says Standard Access is enough for accounts you own or manage. To serve accounts you do not own, you need Advanced Access, and Advanced Access requires App Review and Business Verification.

To read someone else's public data, Meta offers [Business Discovery](https://developers.facebook.com/docs/instagram-platform/instagram-api-with-facebook-login/business-discovery), last updated on August 12, 2026. You send the request with the ID of your own professional account. In `fields` you write `business_discovery.username(their_name)` to get their follower and media counts. You can nest `media` to get their published posts.

The [reference page](https://developers.facebook.com/documentation/instagram-platform/instagram-graph-api/reference/ig-user/business_discovery) lists three permissions: `instagram_basic`, `instagram_manage_insights` and `pages_read_engagement`. The target must also be a business or creator account. Personal accounts are out of reach, and age-gated accounts return nothing.

```bash
# The sample request from the Meta docs (v27.0). Your own professional account ID goes in the path.
curl -i -X GET \
  "https://graph.facebook.com/v27.0/17841405309211844?fields=business_discovery.username(bluebottle){followers_count,media_count}&access_token=<YOUR_USER_ACCESS_TOKEN>"
```

The sample response in the Meta docs shows Blue Bottle Coffee with 267,793 followers and 1,205 media items. At 00:41 Singapore time on November 15, our `instagram/profile` call for the same account returned 519,718 followers and 2,599 posts, with the category "Coffee shop". The live numbers are almost twice the documented ones, so the sample has not kept up with the account. That is harmless, but it is a warning. Estimates of data volume and call counts based on the samples in the Meta docs will come out too small.

Hashtag data goes through [Hashtag Search](https://developers.facebook.com/docs/instagram-platform/instagram-api-with-facebook-login/hashtag-search). The limits are specific. One business or creator account can query 30 unique hashtags in a rolling 7-day window. A queried hashtag holds its slot for 7 days. Reading `recent_media` or `top_media` also counts as a query. Hashtags on Stories are not supported, emoji hashtags are not supported, and sensitive hashtags return a generic error.

You need App Review for the Instagram Public Content Access feature and the `instagram_basic` permission. For competitor monitoring, 30 hashtags a week is usually the bottleneck. The `recently_searched_hashtags` endpoint lists the hashtags you already used this week.

| Meta endpoint | What it reads | Requirements | Hard limits |
| --- | --- | --- | --- |
| Business Discovery | Follower count, media count and posts of other business and creator accounts | Your own professional account, three permissions, Advanced Access for accounts you do not manage | No personal accounts, no age-gated accounts |
| Hashtag Search | Top and recent media for a hashtag | App Review for Instagram Public Content Access and `instagram_basic` | 30 unique hashtags per 7 days, no Story hashtags |
| Media fields | `media_url` and others | Same as above | No `media_url` for videos with licensed audio or for Reels with downloads turned off |
| Rate limits | — | — | Business Use Case limits, with error codes such as 4, 17, 32 and 613 |

The [IG Media reference](https://developers.facebook.com/documentation/instagram-platform/reference/instagram-media) adds one rule that matters for data collection. Videos with copyrighted or licensed audio do not return `media_url`, including audio from the Instagram library. Reels whose owner turned off downloads also lose `media_url` on requests that read other users' media. That covers Business Discovery, tags, mentions, hashtag search and collaborative media. So the Graph API can tell you that a competitor posted a Reel, yet often cannot give you the video file.

The [Graph API rate limit page](https://developers.facebook.com/docs/graph-api/overview/rate-limiting) says Instagram endpoints use Business Use Case limits. The allowance grows with the account's impressions, so small accounts get fewer calls. On November 4, 2026, Meta [released Graph API v27.0](https://developers.facebook.com/blog/post/2026/11/04/introducing-graph-api-v27-and-marketing-api-v27/). The same post says v21.0 is removed on January 21, 2027, so older scripts need an upgrade date. The post also says that new apps can no longer use multi-ID requests, field aliases, JSONP callbacks or asynchronous batch requests. Scripts that batch many lookups into one request must split them for new apps.

The [Facebook Login setup page](https://developers.facebook.com/documentation/instagram-platform/instagram-api-with-facebook-login) lists what this setup does well. It gets and publishes your own media and moderates comments. It also finds posts that mention you, finds hashtagged media and reads basic data about other professional accounts.

Three of those five features are about your own account. Only two touch other accounts: hashtag search, capped at 30 hashtags a week, and reads of other professional accounts, which cannot see personal accounts. Competitor tracking and creator research need data from any account, so neither feature covers them fully. The [permissions reference](https://developers.facebook.com/docs/facebook-login/permissions) says `instagram_basic` depends on `pages_read_user_content` and `pages_show_list`, and each permission request needs a screencast of the login flow.

The Graph API math is easy. Calls cost $0, the reach is narrow, and setup waits on two reviews. Review has its own cost. The [App Review page](https://developers.facebook.com/docs/apps/review) says Meta tests your app to confirm that it uses each requested permission. If Meta cannot test the app, it rejects the whole submission. You must build a working app that a reviewer can log in to before you can read other accounts.

For your own account data (insights, comment moderation, publishing), the Graph API is the first choice. For a batch of personal creators or any hashtag at volume, it cannot help.

## Open-source libraries: instaloader and instagrapi cost $0 in fees

The two libraries that come up most are [instaloader](https://github.com/instaloader/instaloader) and [instagrapi](https://github.com/subzeroid/instagrapi). We read the GitHub API on November 15. instaloader has 13,888 stars, an MIT license and v4.16 released on October 27, 2026, Singapore time. instagrapi has 7,147 stars and shipped 3.2.10, 3.2.11 and 3.2.12 between November 12 and November 14, Singapore time. Both libraries shipped a new release within one month.

The instaloader issue list shows a month of breakage. Between October 16 and November 11, users opened 14 new issues. The table below lists the ones that affect public data.

The [troubleshooting page](https://instaloader.github.io/troubleshooting.html) is direct about IP addresses. Cloud, VPN and public proxy IPs can face much stricter limits for anonymous access, while logged-in access does not seem affected. A batch job on a cloud server will usually need a logged-in account. The Instagram terms restrict automated collection with a logged-in account.

| Issue | Opened | Summary |
| --- | --- | --- |
| [#2786](https://github.com/instaloader/instaloader/issues/2786) | 2026-10-21 | Does it still work reliably in 2026? Persistent 429 errors |
| [#2792](https://github.com/instaloader/instaloader/issues/2792) | 2026-10-30 | Login and load-cookies are broken |
| [#2794](https://github.com/instaloader/instaloader/issues/2794) | 2026-10-31 | Logged-out post downloads broken for others too? |
| [#2797](https://github.com/instaloader/instaloader/issues/2797) | 2026-11-04 | Reels listing and download not working |
| [#2803](https://github.com/instaloader/instaloader/issues/2803) | 2026-11-07 | Download aborted with "302 Found" |

instagrapi uses the private mobile API. It does more than instaloader, with direct messages, uploads and insights, and it needs Python 3.11 or newer. Its README calls private API automation "fragile in production" because account trust, proxies, device state, challenges and rate limits change on their own. It also recommends Instagram's own APIs for account-owned business workflows where they fit.

Open source fits two kinds of users. The first wants to back up an own account or pull a few dozen posts for research. The second is a team with people to maintain proxy pools and account pools for the long term. Per 1,000 rows the price is $0. In staff time, you pay for IPs, accounts, recovery after bans and library upgrades.

## Apify Instagram Scraper: per-result pricing for six actors

Apify lists six Instagram actors of its own in the Store. All six bill a "result" event, and the price tier follows your subscription. The table shows the price per 1,000 results from the Apify public API at 00:36 Singapore time on November 15. The API needs no key. The current price of the main [Instagram Scraper](https://apify.com/apify/instagram-scraper) started on February 20, 2026, and the actor was last modified on November 13.

| Actor | Free | Starter | Scale | Business | Extra charges |
| --- | --- | --- | --- | --- | --- |
| [Instagram Scraper](https://apify.com/apify/instagram-scraper) | $2.70 | $2.30 | $1.90 | $1.50 | — |
| [Instagram Profile Scraper](https://apify.com/apify/instagram-profile-scraper) | $2.60 | $2.30 | $2.00 | $1.60 | Account details: $7.00 (Free) to $4.00 (Business) per 1,000 |
| [Instagram Post Scraper](https://apify.com/apify/instagram-post-scraper) | $1.70 | $1.50 | $1.30 | $1.00 | Post details $1.00 to $0.60 per 1,000; music data $7.00 to $4.00 per 1,000 |
| [Instagram Comments Scraper](https://apify.com/apify/instagram-comment-scraper) | $2.60 | $2.30 | $2.10 | $1.90 | — |
| [Instagram Reel Scraper](https://apify.com/apify/instagram-reel-scraper) | $2.60 | $2.30 | $1.40 | $1.00 | $0.001 per run start; per 1,000: share counts $7.00 to $4.00, video downloads $20.00 to $10.00, transcripts $48.00 to $27.00 |
| [Instagram Hashtag Scraper](https://apify.com/apify/instagram-hashtag-scraper) | $2.60 | $2.30 | $2.10 | $1.90 | — |

![Screenshot of a real Apify public API response for GET https://api.apify.com/v2/acts/apify~instagram-scraper, read at 00:36 Singapore time on November 15, 2026, without a key. The title is Instagram Scraper and modifiedAt is 2026-11-13. The last pricingInfos entry shows PAY_PER_EVENT starting 2026-02-20. Teal boxes mark the FREE price of 0.0027 and the GOLD price of 0.0015 per result, and the 30-day run stats: 18222123 succeeded, 741 failed, 55435 timed out and 14529 aborted.](https://everyinfra.com/articles/best-instagram-scraper/img-shot-apify-pricing.webp)

Apify Instagram Scraper public metadata: $0.0027 per result on Free, $0.0015 on Business, and 30 days of run outcomes. [Apify public API response screenshot](https://api.apify.com/v2/acts/apify~instagram-scraper)

The [Apify docs on Store actors](https://docs.apify.com/platform/actors/running/actors-in-store) say most pay-per-event actors include platform usage in the event price. A few charge platform usage separately, so you should check the Pricing tab first. You can also set a maximum charge when you start a run, and the run stops at that limit.

The [Apify pricing page](https://apify.com/pricing) lists Free at $5 of monthly credit, Starter at $19, Scale at $199 and Business at $999. Prepaid credit that you do not use expires at the end of the cycle. Free users are blocked until the next cycle. Paid users can go over, up to their [platform limit](https://help.apify.com/en/articles/11079614-reaching-platform-limits).

The Instagram Scraper Store page converts plans into rows. Starter costs $2.30 per 1,000 and buys over 8,200 results a month. Scale and Business cost $1.90 and $1.50 and buy about 104,700 and 666,000. Divide the monthly fees of $19, $199 and $999 by these unit prices and you get the same numbers (8,261, 104,737 and 666,000). The monthly fee is prepaid credit.

For tens of thousands of rows a month, the $199 Scale plan is the threshold where the price drops from $2.30 to $1.90. Below 8,200 rows, the $19 Starter plan is enough, and unused credit expires.

| Apify plan | Monthly fee | Instagram Scraper price per 1,000 | Rows the fee buys |
| --- | --- | --- | --- |
| Free | $0 ($5 credit) | $2.70 | About 1,850 |
| Starter | $19 | $2.30 | About 8,200 |
| Scale | $199 | $1.90 | About 104,700 |
| Business | $999 | $1.50 | About 666,000 |

The same public API shows 30 days of run statistics. The Instagram Scraper ran 18,292,828 times. It succeeded 18,222,123 times, or 99.61%. It failed 741 times, timed out 55,435 times and was aborted 14,529 times. 68,866 users ran it in 30 days.

Timeouts outnumber failures by more than 70 times. The Instagram Scraper price list has one event only, result. A run that times out before it writes a result creates no result fee. The pricing page also says most pay-per-event actors include platform usage in the event price.

A thread on r/apify asked which actor is the most cost-efficient for Instagram and TikTok. One reply suggested checking when an actor was last updated, because [anything older than two or three months is probably half-broken](https://www.reddit.com/r/apify/comments/1s81nhe/best_costefficient_apify_actor_for_instagram_and/).

The 30-day stats of all six Instagram actors show large differences in volume and stability:

| Actor | Runs in 30 days | Success rate | Timeouts | Timeout share | Users in 30 days | Runs per user |
| --- | --- | --- | --- | --- | --- | --- |
| Instagram Scraper | 18,292,828 | 99.61% | 55,435 | 0.30% | 68,866 | 266 |
| Instagram Profile Scraper | 10,985,318 | 99.55% | 43,047 | 0.39% | 44,535 | 247 |
| Instagram Post Scraper | 6,183,573 | 99.88% | 6,109 | 0.10% | 21,011 | 294 |
| Instagram Reel Scraper | 3,747,072 | 99.85% | 3,178 | 0.08% | 27,169 | 138 |
| Instagram Comments Scraper | 1,195,021 | 99.68% | 2,346 | 0.20% | 10,493 | 114 |
| Instagram Hashtag Scraper | 826,451 | 99.51% | 2,206 | 0.27% | 22,310 | 37 |

The Profile Scraper has the highest timeout share, 0.39%, and the second-largest volume, with 10.99 million runs in 30 days. The Hashtag Scraper has 22,310 users but only 37 runs per user, the lowest of the six. Failures stay between 110 and 741 for every actor, one or two orders of magnitude below timeouts. So when you estimate real Apify cost, watch timeouts and aborted runs first.

## Bright Data Instagram Scraper API: $1.50 per 1,000, failed records free

The [Bright Data Instagram product page](https://brightdata.com/products/web-scraper/instagram) lists $1.50 per 1,000 records pay as you go. The Scale plan includes 384,000 records and charges $1.30 per 1,000 above that. New accounts get 5,000 free records a month without a card, worth about $7.50 at the pay-as-you-go rate. The page also says you pay only for successfully delivered records, with no charge for failed deliveries. One request can carry up to 5,000 URLs. The "failed deliveries are free" line sits in the pricing headline.

The [Bright Data first-request guide](https://docs.brightdata.com/products/scrapers/instagram/send-first-request) lists the output fields: 26 for profiles, 40 for posts, 27 for Reels and 14 for comments. That is more than our 19, 21, 22 and 11. A synchronous request waits up to one minute. After that it returns HTTP 202 with a `snapshot_id` and continues as an async job. The [Reels collect-all reference](https://docs.brightdata.com/api-reference/scrapers/social-media-apis/instagram-reels-collect-all) says Instagram no longer exposes a Reel publish date to the source this scraper reads. Bright Data removed those two input fields in August 2026.

Bright Data keeps an Apache-2.0 [Python example repository](https://github.com/brightdata/instagram-scraper) on GitHub. Its README is practical. Each call takes one to three minutes because the API runs a job and the SDK waits for it. Each post costs one credit.

You must pass `auto_create_zones=False`. Without it, the SDK tries to create zones for two other products, and that fails on accounts without a payment method ([sdk-python#57](https://github.com/brightdata/sdk-python/issues/57)). The CLI sample output shows 34 fields per post, a little below the 40 in the docs, maybe because the sample is trimmed.

Bulk jobs run asynchronously. The [async request guide](https://docs.brightdata.com/products/scrapers/scrapers-library/async-requests) describes three steps: trigger, poll and download. Each data type has its own `dataset_id`. The [product introduction](https://docs.brightdata.com/products/scrapers/instagram/introduction) lists NDJSON (default), JSON, JSON Lines, CSV and Parquet as output formats. The README adds that snapshots stay downloadable for 30 days. So for a large job you can trigger it, store the snapshot ID and fetch the data hours later.

Bright Data matches the Apify Business tier on price. Its free allowance is larger, its failure policy is the clearest and it documents the most fields. The weak points are speed and the per-row bill at volume.

## TikHub: from $0.001 per request, and every HTTP 200 is billed

TikHub publishes a price list that needs no key. At 00:33 Singapore time on November 15, it showed 157 Instagram endpoints. 85 cost $0.001 per call, 33 cost $0.002 and 39 cost $0.008. Only 8 of the 157 accept free credit, and 8 join the volume discount.

The v1 `fetch_user_posts` endpoint costs $0.001 per call. In the OpenAPI file its `count` parameter has a default of 12 and a maximum of 50. At the default, 1,000 posts take about 84 requests, or $0.083. At 50 per page they take 20 requests, or $0.020. This endpoint needs a user_id. To start from a username, you first call `fetch_user_info_by_username`, also $0.001.

TikHub also has post endpoints that take a username. The v2 `fetch_user_posts` costs $0.002 per call, and its page size is not documented. The v3 `get_user_posts` costs $0.008 per call with up to 50 posts per page, or $0.16 per 1,000. The price list also shows the web_app `fetch_user_posts_and_reels_by_username` at $0.001. The OpenAPI file we read does not include it, so its page size is unknown.

![Horizontal bar chart of the per-call prices of 157 TikHub Instagram endpoints. Three bars: 85 endpoints at $0.001, the longest; 33 at $0.002; 39 at $0.008. A note says only 8 endpoints accept free credit.](https://everyinfra.com/articles/best-instagram-scraper/fig-05-tikhub-price-bar.en.light.svg)

![Screenshot of a real TikHub public price list response for GET https://api.tikhub.io/api/v1/tikhub/user/get_all_endpoints_info, read at 00:33 Singapore time on November 15, 2026, without a key. The header shows code 200 and a message, boxed in teal, saying the request will incur a charge. The time is 2026-11-14 08:33:42 in Los Angeles. Five Instagram endpoints follow: user info by username, v1 posts, v1 comments, v2 posts and web user info, priced 0.001, 0.001, 0.001, 0.002 and 0.001 USD. The v1 posts row is boxed and shows allow_free_credit 0.](https://everyinfra.com/articles/best-instagram-scraper/img-shot-tikhub-prices.webp)

The TikHub price list: the post list costs $0.001 per call and does not accept free credit. [TikHub public price list response screenshot](https://api.tikhub.io/api/v1/tikhub/user/get_all_endpoints_info)

The [TikHub FAQ](https://tikhub.io/faq) is direct about billing. A request that returns HTTP 200 is billed, empty results and repeats included. The minimum top-up is $5 with no maximum. New accounts get $0.05 of free credit, but most endpoints do not accept it.

The usage log and the daily volume discount run on Los Angeles time. The FAQ says the discount steps up from 0% to 50%, but only 8 of the 157 Instagram endpoints take part. Post lists and comments are not among them, so Instagram unit prices stay flat as volume grows. The [TikHub pricing page](https://tikhub.io/pricing) lists no monthly fee.

TikHub wins on breadth and low unit prices. Its profile endpoint costs $0.001 per call, or $1.00 per 1,000 profiles, and comments start at $0.001 per call. Against our numbers, posts differ by 1.8 to 7.2 times at 50 per page ($0.020 against $0.0111 and $0.00278), and by 7.5 to 30 times at the default 12. Profiles differ by 1.8 times.

The risk is that empty results are billed. A wrong username, a renamed account or a deleted account still costs $0.001. On the cheapest v1 path, 100 new accounts first need 100 user_id lookups, which add $0.10 once. After that you store the user_id and skip the lookup.

## Instagram scraper API test: 12 EveryInfra calls for $0.006433

Our catalog lists 18 `instagram/*` capabilities (see the [Instagram API page](/en/instagram-api)). When we read it on November 15, 17 were available and `instagram/comment_replies` was paused. Between 00:26 and 00:45 Singapore time we made 12 calls. They covered profiles, post lists, comments, Reels, hashtags, single posts and Reels search. We also sent one call for an account that does not exist and one call with a wrong parameter on purpose.

| Singapore time | Capability | Request | Result | Charged | Per 1,000 |
| --- | --- | --- | --- | --- | --- |
| 00:26:55 | `instagram/profile` | natgeo | 1 row, 268,127,355 followers, 32,168 posts | $0.000556 | $0.556 |
| 00:27:04 | `instagram/user_posts` | natgeo, `limit` 200, async | 200 posts (113 video, 87 image), done 00:27:56 | $0.000556 | $0.00278 |
| 00:28:07 | `instagram/comments` | a post showing 99 comments, `limit` 100 | 15 rows over 1 h 44 min | $0.000792 | $0.0528 |
| 00:28:27 | `instagram/reels` | natgeo, `limit` 100 | 100 rows with `play_count` | $0.001194 | $0.0119 |
| 00:29:24 | `instagram/hashtag` | coffee, `limit` 100 | 30 rows over 2 h 8 min | $0.000556 | $0.0185 |
| 00:30:37 | `instagram/profile` | unknown account | 0 rows, `empty_result_refunded` | $0 | — |
| 00:31:33 | `instagram/user_posts` | parameter sent as `user` | 422 `missing_param` with a fix | $0 | — |
| 00:31:39 | `instagram/post` | 3 post URLs | 3 rows | $0.001667 | $0.556 |
| 00:32:01 | `instagram/reels_search` | coffee | 503, `error.code` `unavailable`, `reason` `capacity_exhausted`, retry after 900 s | $0 | — |
| 00:41:21 | `instagram/profile` | bluebottle | 519,718 followers, 2,599 posts | $0.000556 | $0.556 |
| 00:41:46 | `instagram/user_posts` | bluebottle, `limit` 50, async | 50 posts, done 00:42:24 | $0.000556 | $0.0111 |
| 00:45:25 | `instagram/reels_search` | coffee (retry) | 503 again, refunded | $0 | — |

Eight of the 12 calls were charged, for $0.006433 in total. Four cost nothing. The post list [`instagram/user_posts`](/en/instagram-api/user_posts) shows the widest gap in this ranking. The catalog price is $0.000556 per call.

natgeo returned 200 posts in one call, from September 8 to November 14, 2026, a span of 67 days. bluebottle posts less often, so a limit of 50 returned 50 posts from June 26 to November 12, a span of 139 days. The same call price bought four times more rows for natgeo, which is why our post price is a range.

Both `user_posts` calls ran as async jobs. The natgeo job started at 00:27:04 and finished at 00:27:56, so 200 posts took 52 seconds. The bluebottle job started at 00:41:46 and finished at 00:42:24, so 50 posts took 38 seconds.

The 202 receipt already states the charge and the per-1,000 price. When the job finishes, you read the results from `poll_url`, and `billing_state` shows whether billing is settled. Bright Data's README quotes one to three minutes per call, so both services need polling at a similar speed. The synchronous capabilities (profile, comments, Reels, hashtag) answered in one request that night.

![Screenshot of a real EveryInfra response for instagram/user_posts, natgeo, limit 200, at 00:27 Singapore time on November 15, 2026. The top half is the 202 receipt with status running, a poll_url and charged_usd 0.000556 boxed in teal next to the per-1,000 price. The bottom half is the poll result at 00:27:56 with status succeeded and count 200 boxed, followed by the first post's post_id, url, media_type, like_count, comment_count, author_username and posted_at.](https://everyinfra.com/articles/best-instagram-scraper/img-shot-ei-response.webp)

One user_posts call: the 202 receipt states the $0.000556 charge, and the finished job returns 200 posts. Key removed. [EveryInfra instagram/user_posts real response screenshot](https://api.everyinfra.com/api/v1/social)

```bash
# Post list: up to 200 posts per call. Slow capabilities return 202 with a poll_url first.
curl -s https://api.everyinfra.com/api/v1/social \
  -H "Authorization: Bearer $EVERYINFRA_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"platform":"instagram","action":"user_posts","params":{"username":"natgeo","limit":200}}'

# Poll the poll_url from the receipt. Read results when status is succeeded.
curl -s "https://api.everyinfra.com$POLL_URL" -H "Authorization: Bearer $EVERYINFRA_API_KEY"
```

Comments and hashtags show what `limit` really means. [`instagram/comments`](/en/instagram-api/comments) on a post that displayed 99 comments, with a limit of 100, returned 15 rows. [`instagram/hashtag`](/en/instagram-api/hashtag) for coffee with a limit of 100 returned 30 rows, all from the last two hours. We bill per call, so short responses raise the per-row price. Comments came to $0.0528 and hashtags to $0.0185 per 1,000. That is still 36 to 140 times below Apify, but 7 to 19 times above the natgeo post list. Use measured row counts for budgets, not the `limit` you send.

![Horizontal bar chart comparing the requested limit with rows returned for five calls. Comments: limit 100, returned 15. Hashtag: limit 100, returned 30. bluebottle posts: limit 50, returned 50. Reels: limit 100, returned 100. natgeo posts: limit 200, returned 200. Light bars show the limit and teal bars show rows returned.](https://everyinfra.com/articles/best-instagram-scraper/fig-04-coverage-bar.en.light.svg)

[`instagram/reels`](/en/instagram-api/reels) costs $0.001194 per call, about twice the post list, and returned 100 Reels over 58 days. 21 of its 22 catalog fields had values, and every row had `play_count`. In the `user_posts` response, `view_count` was empty for all 200 posts, so use the Reels capability when you need plays. The single-post capability [`instagram/post`](/en/instagram-api/post) bills per URL. Three URLs cost $0.001667, or $0.556 per 1,000, the same "one target, one price" model as profiles.

The four free calls each failed in their own way. The unknown account took 29 seconds, then returned `charged_usd` 0 with the reason `empty_result_refunded`. The wrong parameter (`user` instead of `username`) returned 422 `missing_param` at once, with the correct parameter name and a next step.

[`instagram/reels_search`](/en/instagram-api/reels_search) returned 503 twice. The `error.code` was `unavailable`, the `reason` was `capacity_exhausted` and `retry_after` was 900 seconds, and the charge was refunded both times. Its catalog price is $0.007194 per call, the highest of our Instagram capabilities. We got no data from it that night, so it is not in the price table.

Our catalog lists fewer fields than Bright Data: 21 against 40 for posts and 19 against 26 for profiles. The fields with real values are fewer again. If your analysis needs fields that only Bright Data lists, such as collaborators or branded content tags, check its field table first. If a field is not in our catalog, we do not return it.

![Grouped bar chart with three bars for each of four data types: Bright Data documented fields, EveryInfra catalog fields and EveryInfra fields with values in our test. Profiles 26, 19, 17. Posts 40, 21, 15. Reels 27, 22, 21. Comments 14, 11, 9.](https://everyinfra.com/articles/best-instagram-scraper/fig-03-fields-bar.en.light.svg)

| Data | Bright Data documented | EveryInfra catalog | EveryInfra with values | Missing in our test |
| --- | --- | --- | --- | --- |
| Profiles | 26 | 19 | 17 (bluebottle) | natgeo had no `category` |
| Posts | 40 | 21 | 15 | `view_count` empty |
| Reels | 27 | 22 | 21 | — |
| Comments | 14 | 11 | 9 | — |
| Hashtag posts | — | 22 | 17 | `location` set on 10 of 30 |

## What one night of data shows: natgeo, bluebottle and #coffee

Buyers also care whether the data is ready for decisions. We summarized the 400 rows from the 8 charged calls. The numbers below describe this one sample from the early hours of November 15. They show the shape of the data, not the long-term performance of these accounts.

| Sample | Rows | Metric | Result |
| --- | --- | --- | --- |
| natgeo posts (`user_posts`) | 87 images, 113 videos | Median likes | Images 72,542, videos 43,880 |
| natgeo posts (`user_posts`) | 200 | Median and maximum comments | 205.5 and 15,813 |
| natgeo Reels (`reels`) | 100 | Median plays | 1,782,073 (min 595,823, max 35,863,019) |
| natgeo Reels (`reels`) | 100 | Median likes per play | 2.26% |
| natgeo Reels (`reels`) | 100 | Median length | 32.5 seconds |
| bluebottle posts (`user_posts`) | 39 images, 11 videos | Median likes | Images 560, videos 487 |
| #coffee (`hashtag`) | 30 | Median likes, rows with a location | 0 and 10 |

In both accounts, images had a higher median like count than videos. The gap was larger for natgeo, where images led by 65%. A longer window must confirm this. Still, it shows that one `user_posts` response already carries `media_type` and `like_count`, so you can group posts without a detail call. Plays and lengths come only from `instagram/reels`. The `view_count` in `user_posts` was empty, so pull Reels separately for play-based metrics.

All 30 #coffee posts came from the last 2 hours and 8 minutes. Their median like count was 0, and one third carried a location. The hashtag capability returns the newest posts. It answers "who is posting now", not "what went viral". To find hits, pull the authors' profiles and post lists next.

The 15 comments follow the same pattern. They all arrived in the last 1 hour and 44 minutes, the median like count was 0 and none came from a verified account. You get the newest comments, not the top comments.

## Hashtag tracking: how often to check, and what it costs

Hashtag data needs a different calculation. For a busy tag like #coffee, one call of 30 posts covers about two hours. To follow it for a full day at that rate, you check every two hours. That is 12 calls a day, or $0.0067, and about $0.20 for 30 days. A quiet tag may get a few posts a day, so one check a day is enough, which is $0.017 a month. Either way the price depends on how often you check, not on how busy the tag is.

Per-row billing gives a different answer. At that night's rate, #coffee gets about 336 new posts a day. The Apify Hashtag Scraper charges $1.90 to $2.60 per 1,000, so one day costs $0.64 to $0.87, and a month costs $19 to $26. Bright Data at $1.50 per 1,000 comes to about $15 a month. The Meta Hashtag Search is free, but one account can query only 30 unique tags in 7 days. It returns two lists, top media and recent media, and frequent polling of one busy tag runs into rate limits first.

| Approach | One busy tag at the #coffee pace, per month | What limits you |
| --- | --- | --- |
| EveryInfra `instagram/hashtag` | About $0.20 (12 calls a day) | 30 newest posts per call, no pagination |
| Apify Hashtag Scraper | $19 to $26 (about 336 posts a day) | Price per row |
| Bright Data | About $15 before free records | Price per row |
| Meta Hashtag Search | $0 | 30 unique tags per 7 days, rate limits |

One condition matters here. Our `instagram/hashtag` catalog entry has two parameters, `hashtag` and `results_type`, and no pagination parameter. Each call returns the newest batch. The default count is 30, and our call with limit 100 returned exactly 30.

"Every two hours" is an estimate from one night of posting speed. A busy tag at peak hours can move faster, so some posts can be missed. If you need every post, run a small test first. Compare the overlap between two consecutive calls, then set the interval.

## Instagram scraper API cheap: three monthly bills

Unit prices hide monthly fees and free allowances, so we priced three common monthly workloads. Our bill is the catalog price times the number of calls. TikHub is the per-call price times the number of requests. Apify and Bright Data are the per-1,000 price times rows. For Bright Data we subtract the 5,000 free records first. For Apify we compare the usage with the plan fee and take the higher number.

| Workload | EveryInfra | TikHub | Apify (unit price) | Apify (cheapest with plan fee) | Bright Data (after free records) |
| --- | --- | --- | --- | --- | --- |
| A: 100 accounts, 30 new posts each a day, 90,000 posts in 30 days | $1.67 | $3.10 | $135 to $243 | $199 (Scale) | $127.50 |
| B: 10,000 profiles a month | $5.56 | $10.00 | $16 to $26 | $23 (Starter) | $7.50 |
| C: 100,000 comments a month | $5.28 | Not computed (page size not published) | $190 to $260 | $210 (Scale with overage) | $142.50 |

In workload A, we call `user_posts` once per account per day. 3,000 calls at $0.000556 is $1.67. TikHub uses the v1 post endpoint with `count` set to 30, so one page per account per day. 3,000 requests at $0.001 is $3.00. Add the first 100 user_id lookups at $0.10, and the total is $3.10. At the default 12 per page it would take three pages a day, or $9.10.

Apify costs $243 to $135 at Free to Business unit prices. But the Free plan has only $5 of credit, Starter with overage comes to $207, and the $199 of Scale credit covers the usage. The cheapest Apify bill is therefore $199. Bright Data charges 85,000 rows after the free 5,000, at $1.50 per 1,000, for $127.50.

Workload B has the smallest gap. 10,000 profiles cost $5.56 with us, $7.50 with Bright Data after the free records, $10.00 with TikHub and $23 with Apify Starter. If you look up only a few thousand profiles a month, the Bright Data free allowance covers it, and your bill is $0. That beats us.

Workload C uses our measured 15 comments per call, so 100,000 comments need 6,667 calls, or $5.28. Posts with fuller comment pages make it cheaper, and thinner pages make it dearer. The TikHub comment endpoint costs $0.001 per call, but its docs do not give a page size, so we cannot convert it.

The Bright Data README says comments bill one credit each. After the free allowance, 100,000 comments cost $142.50. Comments are the most expensive data type under per-row billing. A popular post can carry thousands of comments, and the row count grows much faster than the post count.

![Grouped bar chart of monthly USD bills for three workloads on a log axis. Workload A, 90,000 posts: EveryInfra $1.67, TikHub $3.10, Bright Data $127.50, Apify Free rate $243. Workload B, 10,000 profiles: EveryInfra $5.56, Bright Data $7.50, TikHub $10.00, Apify $26. Workload C, 100,000 comments: EveryInfra $5.28, Bright Data $142.50, Apify $260, no TikHub bar. A note says Bright Data is net of 5,000 free records a month.](https://everyinfra.com/articles/best-instagram-scraper/fig-02-monthly-bill-bar.en.light.svg)

## What each approach looks like when it fails

A batch job will meet failures, so the shape of a failure matters as much as the price of a success. The six approaches send different signals and bill differently when things go wrong.

| Approach | Typical failure | What you see | Billed? |
| --- | --- | --- | --- |
| Meta Graph API | Rate limit, personal account, more than 30 tags a week | Error codes such as 4, 17, 32, 613; personal accounts not found | Not applicable |
| instaloader | Rate limits, broken login, changed endpoints | 429, 302, login errors (see the issue table) | Not applicable, but the account can be restricted |
| Apify | Timed-out or aborted runs | Run status TIMED-OUT or ABORTED; 55,435 timeouts in 30 days | No results, no result fee; start fees still apply where listed |
| Bright Data | A failed record, a sync request over one minute | Error rows (with `include_errors`); HTTP 202 with `snapshot_id` | Failed deliveries are free |
| TikHub | Wrong username, empty result, repeat request | HTTP 200 with empty data | Every HTTP 200 is billed |
| EveryInfra | Empty result, wrong parameter, no capacity | `empty_result_refunded`; 422 with a fix; 503 with `retry_after` | Not billed, empty results refunded |

We met all three of our failure types on November 15. The wrong parameter failed fastest. The 422 named the missing `username` and listed the supported parameters, so an AI tool can fix the request and send it again.

The 503 carried a `retry_after` of 900 seconds. Waiting 15 minutes is the simple answer. Our retry after 13 minutes still got a 503, because we did not wait the full 900 seconds. The empty result was slowest. The unknown account took 29 seconds, the money went back to the balance and the response showed the refund reason.

The Bright Data examples on GitHub handle one edge case in detail. An account with no recent posts counts as a success with an empty list, and the reason goes into `note`. An account that does not exist counts as a failure, and the message goes into `error`. Under per-row billing, an empty list creates no records and so costs nothing.

TikHub works the other way. It bills by request status, so an empty list behind an HTTP 200 still costs $0.001. A list with many dead accounts pushes the real TikHub unit price above the listed one.

## What changed in the last 30 days

Instagram data tools change fast, so the dates matter. The table lists the events from the last 30 days that touch this ranking. Each row links back to a source in the references. Read it as a reminder to recheck any tool before a large job, including ours.

| Date | Event | Why it matters |
| --- | --- | --- |
| 2026-10-17 | TechCrunch reports criticism of new Meta commercial terms on scraping and AI training | Terms can change between two of your runs |
| 2026-10-21 | instaloader issue #2786 reports persistent 429 errors | Anonymous access from servers gets throttled |
| 2026-10-27 | instaloader v4.16 released | Upgrades follow Instagram changes |
| 2026-10-29 | Meta updates the Instagram Platform overview | Unified Login is now the recommended setup |
| 2026-11-04 | Graph API v27.0 released, instaloader issue #2797 on Reels | New apps lose batch features, Reels listing breaks in one library |
| 2026-11-05 | Meta pauses the disputed terms update | The November 20 date no longer applies |
| 2026-11-13 to 2026-11-14 | Apify Instagram Scraper modified, instagrapi 3.2.12 released | Both tools still ship fixes |
| 2026-11-15 | Our 12 live calls, two Reels searches return 503 | Our keyword Reels search was unavailable that night |

## Five checks before you switch tools

Instagram changes often. Any provider that works today can break next month. These five checks cost a few cents and take a few minutes. They apply to every paid option in this ranking.

| Check | How | Our result on November 15 |
| --- | --- | --- |
| Is it maintained? | Read the last update date, the 30-day run stats or the issue list | The main Apify actor changed on November 13; instaloader got 14 new issues in a month |
| How many rows from a big account? | Use an active account such as natgeo with the maximum `limit` | `user_posts` returned all 200 |
| How far back for a small account? | Use a quiet account and read the date span | bluebottle: 50 posts over 139 days |
| Does an unknown account cost money? | Send a username that does not exist | 0 rows, refunded, 29 seconds |
| What happens with a wrong parameter? | Misspell a parameter name | 422 with the correct name |

The first check is the easiest and the most often skipped. The Apify public API shows `modifiedAt` and 30-day run stats without a key. The Bright Data example repository says a full check runs every Monday and a smaller one every other day. For open source, read the last week of issues.

Checks two and three tell you if your row-based budget is right. With per-request billing, rows per call set the unit price, so test one big and one small account. Checks four and five set the cost of errors. Every list has renamed, deleted and private accounts. Whether empty results cost money becomes a visible sum at tens of thousands of requests.

## Four common jobs and what to use

These are the four most common reasons to buy Instagram data, each with a capability, a rough monthly cost and the case for another provider.

Competitor and brand tracking means following dozens or hundreds of accounts and reporting new posts and engagement every day. Use `instagram/user_posts` per account. Check busy accounts daily and quiet ones weekly. For 100 accounts, that is $0.24 to $1.67 a month. If you only need your own company account, or you also manage comments and messages, use the Meta Graph API.

Creator research means checking follower counts, posting rates and recent engagement for a list of candidates. Start with `instagram/profile` at $0.000556 per account. Then pull `user_posts` or `reels` for the shortlist. Profiles for 1,000 candidates cost $0.56. Under 5,000 candidates a month, the Bright Data free allowance covers the profile step.

Comment and sentiment work means reading the newest comments under a few posts to see what users complain about. Use `instagram/comments` at $0.000792 per call. That night one call returned the newest 15 comments. For a fuller comment history, the Apify Comments Scraper and Bright Data return more rows per post. Their unit price is 28 or more times ours. Replies to comments are paused on our side, so use TikHub or Apify if you need replies.

Hashtag and trend work means following a few tags to see who posts and what. Use `instagram/hashtag`. With the math above, a busy tag costs about $0.20 a month and a quiet one a few cents. Keyword search for Reels (`instagram/reels_search`) failed twice that night. To search Reels by keyword now, you can try the hashtag capability with `results_type: reels`, which we did not test that night.

## When another option is the better choice

Price is one factor. In these cases another approach fits better, or we cannot do the job.

| Your situation | Better choice | Why |
| --- | --- | --- |
| Insights, comment moderation or publishing for your own account | Meta Graph API | First-party API, free, can write, and the data is yours |
| A few thousand profiles a month | Bright Data free allowance | 5,000 free records a month, so the bill can be $0 |
| Thousands of URLs per job, or 40 post fields | Bright Data | Up to 5,000 URLs per request and 40 post fields |
| No code, with buttons, schedules and spreadsheet export | Apify | Store UI with schedules and export, six Instagram actors ready |
| Transcripts or comment replies that we do not offer now | Apify Reel Scraper or TikHub | Apify sells transcript events; TikHub has a replies endpoint; our `instagram/comment_replies` is paused |
| Backing up your own posts once in a while | instaloader | Free, one command, small volume rarely hits limits |

Three more limits are not in the table. Comments come back as the newest dozen or so, not the full history. Keyword Reels search returned 503 twice that night. The post list is an async job, so you write one polling loop.

Each provider has a deeper price guide: [Apify](/en/blog/apify-pricing-explained), [Bright Data](/en/blog/bright-data-pricing-explained) and [TikHub](/en/blog/tikhub-pricing-explained). We also keep a [Bright Data alternative page](/en/alternatives/brightdata) and a [TikHub alternative page](/en/alternatives/tikhub).

We fit a different job. You get posts, Reels and comments in bulk by account or hashtag. You pay per call, empty results are free, and AI tools can call us directly. Our remote MCP server exposes the same capabilities to tools such as Claude and Cursor. The setup is in the steps below.

## FAQ

### What does Reddit say is the best Instagram scraper?

This question comes from the search suggestion "best instagram scraper reddit". In the r/apify thread, the reply did not name one actor. It said to check the last update date, because anything older than two or three months is probably half-broken. It also suggested a first test of your own keywords on free tiers.

In r/scrapingtheweb, [a thread asks how people scrape public profiles without getting blocked](https://www.reddit.com/r/scrapingtheweb/comments/1vrn0d4/how_are_you_guys_scraping_public_instagram/). The poster does not want to build login, cookie and request-timing logic. Both threads say the same thing: check that a tool still works before you compare prices.

### Is there an Instagram scraper API free for long-term use?

Search suggestions include "instagram scraper api free" and "best instagram scraper free". The long-term free options are the Meta Graph API, limited to professional accounts, and open-source libraries, where you handle rate limits yourself. Free allowances on paid services: Bright Data gives 5,000 records a month. Apify Free gives $5 a month, about 1,850 rows at the Instagram Scraper Free rate. TikHub gives new accounts $0.05, and most Instagram endpoints do not accept it. We give $1 of trial credit for 24 hours, which buys about 1,800 profile lookups or hundreds of thousands of posts through the post list.

### Is Instagram scraping legal?

"is instagram scraping legal" and "instagram scraping against tos" both appear in search suggestions. We do not give legal advice. Here are the texts. The [Instagram Terms of Use](https://help.instagram.com/581066165581870) prohibit "accessing or collecting information in an automated way without our express permission". Updated terms take effect on January 20, 2027. A [Help Center page](https://help.instagram.com/740480200552298) says accounts can be restricted when systems detect unauthorized scraping.

In October, Meta changed its commercial terms and drew criticism over scraping and AI training. [TechCrunch reported it on October 17](https://techcrunch.com/2026/10/17/meta-removes-language-that-raised-scraping-and-ai-training-concerns/), and [Nieman Lab covered it](https://www.niemanlab.org/2026/10/metas-new-commercial-terms-will-allow-the-scraping-of-news-sites-legal-experts-say/). According to [MediaPost](https://www.mediapost.com/publications/article/419294/meta-pauses-data-scraping-terms-following-publishe.html), Meta said on November 5 that those updates were paused and would not take effect on November 20. Ask your own lawyer about your use case.

### Can the Instagram Graph API get posts from other accounts?

This is the suggestion "instagram graph api get posts". Yes, for business and creator accounts only. Use Business Discovery and request `business_discovery.username(their_name){media}` on your own professional account ID. Personal accounts are out of reach, age-gated accounts return nothing and videos with licensed audio have no `media_url`. To read accounts you do not manage, your app needs Advanced Access, which means App Review and Business Verification.

### Instagram scraper API cheap: which one costs the least?

Per 1,000 posts, with public prices and our tests on November 15, EveryInfra costs the least ($0.00278 to $0.0111). TikHub comes next at $0.020 to $0.083, depending on the page size you set. Apify and Bright Data sit between $1.00 and $2.70. Per 1,000 profiles, we measured $0.556 and TikHub lists $1.00, so the gap is under two times. Under 5,000 profiles a month, Bright Data costs $0 inside its free allowance. Meta and open source cost $0 per call, and you pay in review time and maintenance.

### Which Instagram scraper on GitHub still works?

Suggestions include "best instagram scraper github" and "instagram scraper api github". Our GitHub reads on November 15 show both main libraries active. instaloader has 13,888 stars and released v4.16 on October 27, Singapore time. instagrapi has 7,147 stars and released 3.2.12 on November 14, Singapore time.

The recent instaloader issues center on 429 errors, logins and the Reels listing. The instagrapi README warns that private API automation is fragile in production. GitHub also hosts the Bright Data Python examples. That code is open, but it calls the paid Bright Data API, so you still pay per row.

### Does an Instagram scraper API charge for failed requests?

Each paid option has its own rule. EveryInfra refunds empty results, returns 422 for wrong parameters without a charge and refunds 503 capacity errors. All four failures in our test on November 15 cost $0. Bright Data says failed deliveries are free. Apify bills result events, so no results means no result fee, but some actors add a start fee (the Reel Scraper charges $0.001 per run). TikHub bills every HTTP 200, including empty results and repeats.

## Getting started: sign up, create a key, send a request

First, create an account on the [EveryInfra marketplace](/en/market). You do not need a card. Star two of our GitHub repositories to claim $1 of trial credit in the console. The credit is valid for 24 hours. You can also top up. There is no monthly fee.

Second, create an API key in the console and store it as `EVERYINFRA_API_KEY`. Third, follow the [quickstart](/en/docs#quickstart) and send the `user_posts` request above, then poll the `poll_url` from the receipt. The [Instagram API page](/en/instagram-api) and the [pricing page](/en/pricing) list every parameter and price. The same request shape also works for our [TikTok API](/en/tiktok-api).

Add our remote MCP server to the config of an AI tool such as Claude or Cursor. The tool then lists a set of `everyinfra_*` tools. The three you use most are `everyinfra_list_capabilities`, `everyinfra_call_api` and `everyinfra_get_job`. The last one reads async results. See the [MCP server page](/en/mcp-server) and the [remote MCP setup guide](/en/build/remote-mcp-setup) for details.

```text
{
  "mcpServers": {
    "everyinfra": {
      "type": "http",
      "url": "https://api.everyinfra.com/mcp",
      "headers": { "Authorization": "Bearer ${EVERYINFRA_API_KEY}" }
    }
  }
}
```

After that, you can ask the AI tool for the latest 200 natgeo posts, sorted by likes, top 10. It calls `instagram/user_posts` once, for $0.000556.

## References

1. [Instagram Platform overview](https://developers.facebook.com/docs/instagram-platform/overview), Meta for Developers, updated October 29, 2026, read November 15, 2026
1. [Business Discovery](https://developers.facebook.com/docs/instagram-platform/instagram-api-with-facebook-login/business-discovery), Meta for Developers, updated August 12, 2026
1. [IG User Business Discovery reference](https://developers.facebook.com/documentation/instagram-platform/instagram-graph-api/reference/ig-user/business_discovery), permission list
1. [Hashtag Search](https://developers.facebook.com/docs/instagram-platform/instagram-api-with-facebook-login/hashtag-search), Meta for Developers, updated August 17, 2026
1. [IG Media reference](https://developers.facebook.com/documentation/instagram-platform/reference/instagram-media), `media_url` rules
1. [Graph API rate limits](https://developers.facebook.com/docs/graph-api/overview/rate-limiting), Business Use Case limits
1. [Introducing Graph API v27.0 and Marketing API v27.0](https://developers.facebook.com/blog/post/2026/11/04/introducing-graph-api-v27-and-marketing-api-v27/), Meta, November 4, 2026
1. [App Review](https://developers.facebook.com/docs/apps/review), Meta for Developers
1. [Features reference: Instagram Public Content Access](https://developers.facebook.com/docs/apps/review/feature#reference-INSTAGRAM_PUBLIC_CONTENT_ACCESS), Meta for Developers
1. [Permissions reference](https://developers.facebook.com/docs/facebook-login/permissions), Meta for Developers
1. [Instagram API with Instagram Login](https://developers.facebook.com/documentation/instagram-platform/instagram-api-with-instagram-login), Meta for Developers
1. [Instagram API with Unified Login](https://developers.facebook.com/documentation/instagram-platform/instagram-api-with-unified-login), Meta for Developers
1. [Instagram API with Facebook Login](https://developers.facebook.com/documentation/instagram-platform/instagram-api-with-facebook-login), Meta for Developers
1. [Instagram Terms of Use](https://help.instagram.com/581066165581870), read November 15, 2026
1. [Instagram Terms of Use preview](https://help.instagram.com/2159268501666222), effective January 20, 2027
1. [Why your account has been restricted for data scraping](https://help.instagram.com/740480200552298), Instagram Help Center
1. [instaloader](https://github.com/instaloader/instaloader), GitHub, 13,888 stars, v4.16 on 2026-10-27 SGT
1. [instaloader issue #2786](https://github.com/instaloader/instaloader/issues/2786), 2026-10-21
1. [instaloader issue #2792](https://github.com/instaloader/instaloader/issues/2792), 2026-10-30
1. [instaloader issue #2794](https://github.com/instaloader/instaloader/issues/2794), 2026-10-31
1. [instaloader issue #2797](https://github.com/instaloader/instaloader/issues/2797), 2026-11-04
1. [instaloader issue #2803](https://github.com/instaloader/instaloader/issues/2803), 2026-11-07
1. [instaloader releases](https://github.com/instaloader/instaloader/releases), GitHub
1. [instaloader troubleshooting](https://instaloader.github.io/troubleshooting.html), limits for cloud and VPN IPs
1. [instaloader on PyPI](https://pypi.org/project/instaloader/)
1. [instagrapi](https://github.com/subzeroid/instagrapi), GitHub, 7,147 stars, 3.2.12 on 2026-11-14 SGT
1. [instagrapi on PyPI](https://pypi.org/project/instagrapi/)
1. [Actors in Store](https://docs.apify.com/platform/actors/running/actors-in-store), Apify docs, pay-per-event pricing
1. [Usage and resources](https://docs.apify.com/actors/running/usage-and-resources), Apify docs
1. [Reaching platform limits](https://help.apify.com/en/articles/11079614-reaching-platform-limits), Apify Help Center, September 4, 2026
1. [Apify public API: apify~instagram-scraper](https://api.apify.com/v2/acts/apify~instagram-scraper), read 00:36 SGT on November 15, 2026
1. [Instagram Scraper](https://apify.com/apify/instagram-scraper), Apify Store
1. [Instagram Profile Scraper](https://apify.com/apify/instagram-profile-scraper), Apify Store
1. [Instagram Post Scraper](https://apify.com/apify/instagram-post-scraper), Apify Store
1. [Instagram Comments Scraper](https://apify.com/apify/instagram-comment-scraper), Apify Store
1. [Instagram Reel Scraper](https://apify.com/apify/instagram-reel-scraper), Apify Store
1. [Instagram Hashtag Scraper](https://apify.com/apify/instagram-hashtag-scraper), Apify Store
1. [Apify pricing](https://apify.com/pricing), read November 15, 2026
1. [Bright Data Instagram Scraper API](https://brightdata.com/products/web-scraper/instagram), read November 15, 2026
1. [Bright Data Web Scraper pricing](https://brightdata.com/pricing/web-scraper), read November 15, 2026
1. [Bright Data: send your first request](https://docs.brightdata.com/products/scrapers/instagram/send-first-request), fields and response times
1. [Bright Data: Instagram reels collect all](https://docs.brightdata.com/api-reference/scrapers/social-media-apis/instagram-reels-collect-all), publish date input removed in August 2026
1. [Bright Data: Instagram Scraper API introduction](https://docs.brightdata.com/products/scrapers/instagram/introduction), output formats
1. [Bright Data: async requests](https://docs.brightdata.com/products/scrapers/scrapers-library/async-requests)
1. [Bright Data Instagram scraper Python examples](https://github.com/brightdata/instagram-scraper), GitHub
1. [brightdata/sdk-python issue #57](https://github.com/brightdata/sdk-python/issues/57), GitHub
1. [TikHub price list API](https://api.tikhub.io/api/v1/tikhub/user/get_all_endpoints_info), read 00:33 SGT on November 15, 2026, no key
1. [TikHub OpenAPI](https://api.tikhub.io/openapi.json), `count` default 12, maximum 50, for v1 `fetch_user_posts`
1. [TikHub FAQ](https://tikhub.io/faq), billing rules
1. [TikHub pricing](https://tikhub.io/pricing)
1. [EveryInfra catalog](https://api.everyinfra.com/api/v1/social/catalog), read November 15, 2026
1. [r/apify: most cost-efficient actor for Instagram and TikTok](https://www.reddit.com/r/apify/comments/1s81nhe/best_costefficient_apify_actor_for_instagram_and/)
1. [r/scrapingtheweb: scraping public Instagram profiles without getting blocked](https://www.reddit.com/r/scrapingtheweb/comments/1vrn0d4/how_are_you_guys_scraping_public_instagram/)
1. [TechCrunch: Meta removes language that raised scraping and AI training concerns](https://techcrunch.com/2026/10/17/meta-removes-language-that-raised-scraping-and-ai-training-concerns/), October 17, 2026
1. [Nieman Lab: Meta's new commercial terms and news site scraping](https://www.niemanlab.org/2026/10/metas-new-commercial-terms-will-allow-the-scraping-of-news-sites-legal-experts-say/)
1. [MediaPost: Meta pauses data scraping terms](https://www.mediapost.com/publications/article/419294/meta-pauses-data-scraping-terms-following-publishe.html)
