InstagramPOST /v1/instagram/post_count

Instagram Post Count Scraper API

The number of posts on an Instagram account, exact wherever Instagram shows it. Rounded estimates such as 32K are returned only when you allow them.

Cost
1 credit
Blocks and errors
Refunded
Cache hits
Free
Response fields
5
Limits
Rounded counts only with allow_estimatedAll limits

Updated ยท Maintained by the Scrape Everything team

What the Instagram Post Count Scraper API does

The Instagram Post Count API answers one question: how many posts does this account have? It returns post_count as a whole number, with the username, numeric user ID, the privacy flag and is_estimated. For public accounts the count is usually exact, even where the profile page rounds it to 32K or 1.2M. When only that rounded figure is visible, for example for a large private account, the request fails with 422 ESTIMATE_ONLY and costs nothing, unless you send allow_estimated: true; then you get the rounded number and is_estimated is true. The Instagram profile endpoint returns post_count too, but for large accounts it can be the rounded figure. Each lookup costs 1 credit.

What you get

Top-level fields of the response. Every field is typed and documented; nullable fields are null when the platform does not show them.

FieldTypeDescription
usernamestringInstagram username
user_idstring | nullInstagram numeric user ID
post_countintegerNumber of posts
is_estimatedbooleanpost_count is a rounded value (only with allow_estimated=true)
is_privatebooleanAccount is private

Request example

Send the API key as a Bearer token. The body is a small JSON object.

curl -X POST https://api.scrapeeverything.com/v1/instagram/post_count \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"username":"natgeo"}'
ParameterRequiredDescription
usernameYesInstagram username, @handle or profile URL.
allow_estimatedNoAccept a rounded count (such as 32K) when no exact count is visible. Without it such profiles return 422 ESTIMATE_ONLY at no charge.

Response example

A real response from the live API, captured on November 12, 2026 for the request above. Lists are cut to two items and long links and texts are shortened.

200 OK
{
  "success": true,
  "data": {
    "username": "natgeo",
    "user_id": "787132",
    "post_count": 32160,
    "is_estimated": false,
    "is_private": false
  },
  "meta": {
    "request_id": "req_OgHkwkHROwRHH9JN0Wj1",
    "scraper": "instagram.post_count",
    "cached": false,
    "cached_at": null,
    "cache_age_seconds": null,
    "credits_charged": 1,
    "credits_remaining": 99,
    "duration_ms": 1082
  }
}

Try it with your own input: open this endpoint in the playground with your 100 free credits. Errors use the same envelope with success: false and a documented code; which of them are billed is answered below.

How much does the Instagram Post Count Scraper API cost?

Each request costs 1 credit, so 1,000 requests use 1,000 credits. You are charged only when a request returns data or a definitive answer. Credits come in one-time packs that never expire; the cards below show what 1,000 requests cost with each pack. New accounts get 100 free credits.

  • Builder pack

    $0.80

    25,000 credits for $19.99

  • Growth pack

    $0.60

    500,000 credits for $299.00

  • Scale pack

    $0.50

    1,200,000 credits for $599.00

See pricing for all packs and rate limits.

Which requests are billed and which are refunded?

A request is billed (1 credit) when it returns data or a definitive answer. A 404 with a code such as NOT_FOUND or PRIVATE_ACCOUNT means the target is missing or not public, so drop it from your list instead of retrying. Blocks, timeouts and errors on our side are refunded automatically, and invalid requests are never charged.

  • Billing: 1 credit per lookup. 422 ESTIMATE_ONLY is not charged. 404 NOT_FOUND and AGE_RESTRICTED are definitive answers and are billed; blocks, timeouts and a profile page without a visible count are refunded.
  • allow_estimated takes true or false (the strings "true", "1", "yes" and their opposites work too). Leave it out to get exact counts only.
  • Caching: with cache_days (1 to 14) a repeat lookup is free. nasa, @nasa and the profile URL share one entry, but a request with allow_estimated: true is cached separately from one without.

Every billed and refunded case is listed under credits and billing and errors.

Use cases

  • Measure posting frequency: two exact counts a week apart give the number of posts published in between, minus any deleted.
  • Check a list of accounts for activity before outreach: a count that has not changed in a month points to a dormant account.
  • Feed exact post totals into dashboards where a rounded 1.2M would hide week-to-week changes.

What are the limits of the Instagram Post Count Scraper API?

Each request looks up one target, given as username. New accounts can send 60 requests a minute, rising to 300 a minute once your purchases total $19.99 or more. Every endpoint returns public data only, never private or login-only content; the limitations and notes below list what this one leaves out.

Limitations: Unofficial API: not affiliated with or endorsed by the platform. Public data only. Private accounts return profile fields only; posts show at most 15 newest comments; highlights come with titles and covers, not the stories inside; like and comment counts in the posts list are often null (the single post endpoint returns them), and the link in bio can be null.

  • Public accounts usually get an exact count. Otherwise only the count on the profile page is visible, which Instagram rounds for large accounts (32K, 1.2M).
  • A rounded count is returned only with allow_estimated=true, and then is_estimated is true. Without it the request fails with 422 ESTIMATE_ONLY and no credits are charged.
  • Missing and age-restricted accounts return 404 (code AGE_RESTRICTED for the latter).

Need more than that? Rate limits explains the per-minute and concurrency limits, or contact us for higher limits.

Questions

Why did I get 422 ESTIMATE_ONLY?

Only Instagram's rounded figure (for example 32K) was visible for that account. The request is not charged. Send allow_estimated: true to accept the rounded number; is_estimated is then true.

Is the count always exact?

When is_estimated is false, yes. A rounded value is only returned when you send allow_estimated: true, and is_estimated then says so.

Does it work for private accounts?

Yes. Instagram shows a private account's post count on its profile page. When that figure is shown in full you get it as an exact count; when it is rounded, you need allow_estimated.

Should I use this or the profile endpoint?

Use the profile endpoint (1 credit) when you also want bio, followers and flags. Use this one when the post count itself has to be exact, or when you need to know that it is not.

Can I re-read a result without paying again?

Yes. Send cache_days (1 to 14) and a repeat request for the same target within that window is served from your cache for free.

Use the Instagram Post Count Scraper API without code

Open this endpoint in the dashboard playground, switch to Multi and paste up to 500 username values, one per line. Each line runs as one request (1 credit) and the results download as CSV or JSON. In n8n, Make, Zapier or Google Sheets, send the same request from a workflow or a sheet.

Instagram guides and API reference

More Instagram endpoints

Start with 100 free credits.

Continue with Google, create an API key and send your first request in under a minute.

Get 100 free credits