Skip to main content

Social Media API

Instagram API

Read any public Instagram profile, post, reel, or story as structured JSON — with comments, followers, and search — without Meta's App Review or per-account authorization.

  • Any public account, post, reel, or story — not just accounts that authorized your app
  • Skip Meta's App Review, OAuth, and 200-call-per-hour token limits
  • Three API versions for redundancy on a platform that changes often

$0.05 free credit on sign-up · no credit card · from $0.002/request

One request, structured JSON

terminal
1curl -X GET "https://api.tikhub.io/api/v1/instagram/v2/fetch_user_info?username=instagram" \
2 -H "Authorization: Bearer YOUR_API_KEY"
response.json
1{
2 "code": 200,
3 "data": {
4 "user": {
5 "pk": "25025320",
6 "username": "instagram",
7 "full_name": "Instagram",
8 "is_verified": true,
9 "follower_count": 672000000,
10 "following_count": 175,
11 "media_count": 7980,
12 "biography": "Discover what's next on Instagram.",
13 "profile_pic_url": "https://...",
14 "is_business": true,
15 "category": "Internet company"
16 }
17 }
18}

Get your API key at user.tikhub.io/dashboard/api — or follow the getting-started guide.

FastPay-as-you-goScales to millions99.9% uptimeWell-documentedNo app review

What's in the Instagram API

TikHub's Instagram API spans three series — V2 and V1 visitor-view, plus a real-time V3 — covering public posts, reels, stories, user profiles, comment threads, follower lists, search, locations, and music. Skip Meta's app review and rate-limit gymnastics: authenticate with one TikHub key and get structured JSON back for any public account. Start with the V2 series, and switch to V3 when you need real-time data.

Instagram V2 API (recommended)

ProfilesPosts & reelsStories & highlightsComments & repliesFollowers/followingSearch: users/reels/hashtagsLocationsMusic

Instagram V1 API

Profiles & aboutPosts & reelsCommentsHashtagsLocations & citiesExplore sectionsRelated profilesSearch

Instagram V3 API (real-time)

ProfilesPosts & reelsStoriesComments + translationSearchExplore feedRecommended reels

Any public account — no App Review, no authorization

The official Graph API only returns data for business/creator accounts that have explicitly connected to your Meta app, after you pass App Review. TikHub reads publicly available data for any public account — profiles, posts, reels, stories, comments, followers — with one key and zero per-account authorization.

TikHubInstagram Graph API
Any public account, not just authorized ones
Stories & highlights
No App Review or OAuth flow
Three API versions for resilience

Instagram API endpoints

A reference of the most-used Instagram endpoints. Browse the full set in the API reference or the documentation.

Instagram V2 API (Visitor View — recommended default)

The most stable and detailed of the visitor-view series — start here. Visitor-view data may be cached and can lag the live values by a few days; use the V3 series when you need real-time numbers.

Use caseEndpointDocs
Get user info/api/v1/instagram/v2/fetch_user_info
Get user posts/api/v1/instagram/v2/fetch_user_posts
Get user reels/api/v1/instagram/v2/fetch_user_reels
Get user stories/api/v1/instagram/v2/fetch_user_stories

Instagram V1 API (Visitor View)

The widest endpoint coverage — locations, cities, the explore feed, and related profiles — also visitor-view (may be cached). Several endpoints offer V2/V3 variants that return cleaner data.

Use caseEndpointDocs
Get user info by username/api/v1/instagram/v1/fetch_user_info_by_username
Get user info by username (V2)/api/v1/instagram/v1/fetch_user_info_by_username_v2
Get user info by username (V3)/api/v1/instagram/v1/fetch_user_info_by_username_v3
Get user info by ID/api/v1/instagram/v1/fetch_user_info_by_id

Instagram V3 API (Real-time)

Use V3 when you need up-to-the-minute counts. It also adds comment/caption translation, a recommended-reels feed, and former-username lookups not in the visitor-view series.

Use caseEndpointDocs
Get user ID by username/api/v1/instagram/v3/get_user_id_by_username
Get user profile/api/v1/instagram/v3/get_user_profile
Get user brief info/api/v1/instagram/v3/get_user_brief
Get user about info/api/v1/instagram/v3/get_user_about

Tips & troubleshooting

Hard-won operational notes for working with Instagram data in production.

Which version to call: V2 by default, V3 for real-time

TikHub ships three Instagram series. V1 and V2 are visitor-view; V3 is real-time. The recommended default is the V2 series — it's the most stable and detailed of the visitor-view APIs and covers the widest set of common needs. Reach for the V3 series specifically when you need up-to-the-minute data, comment/caption translation, a recommended-reels feed, or former-username history.

Visitor-view data can be cached (counts may lag)

Because V1 and V2 are visitor-view, some fields — especially counts and statistics like follower, like, and comment totals — are NOT guaranteed real-time and can take a few days to reflect the live values. In practice there's roughly a 5% chance that stats on a very recently posted item aren't yet real-time. That's expected for the visitor-view series, not a bug. When a number has to be exact and current, fetch it from the V3 real-time series instead.

Data discrepancies vs the Instagram app

If the data a TikHub endpoint returns differs from what you see in the Instagram app — different like counts, comment counts, or similar — it's almost always visitor-view caching; re-check the same value through the V3 series. If a discrepancy persists on the real-time series, contact TikHub customer support so they can investigate.

Username vs numeric user ID

Instagram identifies accounts by both a public username and a stable numeric user ID (pk). Usernames change; IDs don't. If you're storing accounts over time, resolve the username to a user ID once and key your records on the ID — then you won't lose an account when its handle changes. The user-info endpoints accept either, and helper endpoints convert a post shortcode (the code in an instagram.com/p/<shortcode> URL) to a media ID and back.

Stories and highlights are time-sensitive

Stories live for 24 hours, so the stories endpoint only returns what's currently active on an account; highlights are the curated, permanent collections and are available any time. If you need a story after it expires you must have captured it while live — schedule collection rather than expecting historical stories on demand.

Do I need an Instagram or Meta developer account?

No. Create a TikHub account, generate an API key, and call REST endpoints — no Meta developer app, no App Review, and no OAuth. TikHub returns publicly available Instagram data.

How is this different from the official Instagram Graph API?

The Graph API requires a Meta developer app, App Review, and only covers accounts that have authorized your app. TikHub reads public data for any public account — no app review, no per-account authorization, one API key.

Is using a Instagram API like this legal?

TikHub returns publicly available data — the same content anyone can see without logging in. US courts (hiQ v. LinkedIn) have held that scraping public data is not a CFAA violation. That said, Instagram's Terms of Service restrict automated access, so account or IP blocks are a real operational risk; TikHub manages that infrastructure for you. You are responsible for how you use, store, and process the data you retrieve.

What are the rate limits?

The default rate limit is 10 requests per second. RPS plans scale it up — 20 RPS at $5/month through 100 RPS at $55/month — and enterprise accounts get custom limits above 100 RPS.

How much does the Instagram API cost?

The Instagram API is billed at $0.002 per request, pay-as-you-go with no monthly minimum. Automatic daily volume discounts apply at high request volumes, and new accounts get $0.05 free credit — no credit card required.

Instagram API: an unofficial alternative to the Graph API in 2026

TikHub's Instagram API lets developers read public Instagram data — profiles, posts, reels, stories, comments, and followers — through plain REST calls, without Meta's App Review or per-account authorization. Here's how it works, how it differs from the official Graph API, where its limits are, and when to use which.

How does the Instagram API work?

What is the Instagram API?

The TikHub Instagram API is a RESTful interface that returns structured JSON for publicly available Instagram content. You request a profile, post, reel, story, or comment thread by username, ID, or URL and receive clean, typed data — no need to run a headless browser, solve Instagram's request signing, or rotate residential proxies yourself.

It's deliberately positioned as an alternative to Meta's official Graph API. Where the Graph API only exposes business and creator accounts that have explicitly connected to your reviewed Meta app, the TikHub Instagram API reads public data for any public account, with one key and no per-account authorization.

How do you access and use it?

Create a free TikHub account, generate an API key, and make an HTTP GET request with the key in the Authorization header. Identify the account or content with a username, a numeric user ID, or a public Instagram URL, and you get JSON back immediately.

Because it's a standard REST API, you can call it from any language or no-code tool. Most workflows start by resolving a username to a user ID, then paginating that user's posts or reels, or pulling a single post and its comments by URL.

What programming languages are supported?

Any language that speaks HTTP — Python, JavaScript/TypeScript, Go, Java, PHP, Ruby, and more. Python is the most common for data and AI work, and an official SDK is available, but the API is language-agnostic. The same request shape works from a backend service, a serverless function, or an automation platform like Zapier or n8n.

What are the benefits of using the Instagram API?

How does it compare to the official Graph API?

The Graph API is sanctioned but narrow and heavy: you build a Meta app, pass App Review, and then only see accounts that authorize it, under a 200-call-per-hour token limit. For most data and research use cases — analyzing public creators you don't control — that model simply doesn't fit.

The TikHub Instagram API removes the app, the review, and the per-account authorization. You read public profiles, posts, reels, stories, comments, and followers for any public account at a flat per-request price, with a 10-RPS default that's an order of magnitude above the Graph API's per-token ceiling.

What are the time-saving advantages?

Skipping App Review alone saves days to weeks of process. Beyond that, you avoid building and babysitting an Instagram scraper — a notoriously brittle thing, given how often Instagram rotates its internal endpoints. TikHub absorbs that churn and ships V1/V2/V3 fallbacks so your integration keeps working through platform changes. Your team spends its time on analysis and product, not on keeping a scraper alive.

Who benefits — marketers, developers, or researchers?

Marketers and agencies vet influencers, benchmark competitor accounts, and analyze reels engagement with real numbers. Developers get a clean data layer for social apps and CRM-enrichment tools without owning scraping infrastructure. Researchers and AI teams pull posts, captions, and comments at scale for sentiment analysis, trend studies, and training datasets — all as structured JSON ready to ingest.

What are the limitations of the Instagram API?

What data is and isn't available?

The API returns publicly available data only — public profiles, posts, reels, public stories while they're live, comments, and follower lists. Private accounts, direct messages, and non-public insights are not accessible. It is read-only by design: there are no endpoints to post, comment, or follow on behalf of an account.

Are there rate limits or reliability considerations?

The default rate limit is 10 requests per second, scalable with RPS plans. The main reliability consideration is Instagram's own volatility: it changes internal endpoints often, which is exactly why TikHub provides V1/V2/V3 of the core endpoints. Build the fallback into your client and your integration stays resilient when Instagram shifts something on its side.

How fresh and complete is the data?

Profile, post, and reel data reflects the current public state of the account. Stories are time-boxed to their 24-hour window. Paginated endpoints (posts, comments, followers) return results in cursor-based pages and may return fewer items than requested per call — keep following the cursor to collect the full set. None of this requires the account to authorize you, which is the whole point.

What are common use cases for the Instagram API?

How is it used for influencer and competitive analysis?

Brands and agencies resolve a creator's profile, pull full post and reel history, and compute real engagement rates rather than trusting a media kit. Comparing several accounts surfaces who's growing, what content performs, and how audiences overlap. Comment threads add a qualitative layer — sentiment, recurring questions, and brand mentions — that pure follower counts miss.

How does it power AI and data products?

Because responses are structured JSON, the Instagram API feeds AI pipelines directly: captions and comments become text corpora for sentiment and topic models, image URLs and metadata support multimodal datasets, and the whole feed can back a retrieval pipeline over creator content. CRM-enrichment and social-listening products use it as their underlying data source.

How is it used for trend and content research?

Hashtag and search endpoints let researchers map how a trend moves through fashion, beauty, food, and lifestyle communities — the categories Instagram leads. Tracking the same hashtags and accounts over time turns anecdote into a measurable trend line, useful for content strategy, market research, and forecasting.

Are there alternatives to the Instagram API?

What other Instagram data tools exist?

The alternatives mirror the rest of the space: Meta's official Graph API (sanctioned but limited to authorizing business/creator accounts after App Review), open-source scrapers like instagrapi (free, Python, but they need a logged-in session and break on Instagram changes), and marketplace actors that wrap scraping behind a hosted run. Each trades off access, reliability, and maintenance differently.

Which option is best for different needs?

If you only need data for accounts you control or that authorize your app, the Graph API is the sanctioned route. For a throwaway script with no uptime requirement, an open-source library can do. But for production access to any public account — reliably, without App Review and without maintaining a scraper through Instagram's frequent changes — a managed API like TikHub is usually the most practical and cost-effective choice.

One key, every platform

The Instagram API shares its key and JSON format with 15 other platforms — adding Instagram or Douyin is a one-line change.

Start free