Instagram Basic Display API Alternative: What to Use Now
No single Instagram Basic Display API alternative exists. Use Instagram Login for your own account, oEmbed for posts, or a public-data API for the rest.
By Scrape Everything team · · Updated · 11 min read
Last updated: November 9, 2026
Short answer: there is no single Instagram Basic Display API alternative, because Meta split the old use cases apart. If you own the account, move to the Instagram API with Instagram Login, which only works with Business or Creator accounts. To show a few specific posts, use oEmbed. To read public profiles and posts from accounts you don't own, use a public-data API that returns JSON from a username.
What replaced the Instagram Basic Display API?
The Basic Display API was the easy path. Any Instagram user, personal accounts included, could authorize your app, and you got their profile and media back. Portfolio sites, "latest posts" widgets and a long list of WordPress plugins ran on it.
Meta's current answer is the Instagram API with Instagram Login, launched in 2024. It looks familiar: the user logs in with Instagram, and no Facebook Page is needed. The catch is the account type. Meta's docs describe it as an API for Instagram professionals, meaning businesses and creators. Its sibling, the Instagram API with Facebook Login, also serves professional accounts, but those accounts must be linked to a Facebook Page.
So which of these describes you?
- You show your own (or a client's) feed, and that account can be switched to Creator or Business.
- You embed a handful of specific posts.
- You read data from public accounts you don't control: competitors, creators, or a client who won't hand over a login.
Does the new Instagram API work with personal accounts?
Not according to Meta. Some plugin help pages blur this, but Meta's own Instagram Platform docs say your app users must have a professional account. If a page tells you a personal account connects fine, check which API it actually calls.
For the read-only part of what Basic Display used to do, showing a profile's public bio and counts, the Instagram profile API needs no user authorization: send a username, get the profile as JSON for 1 credit. It can't read private accounts or anything a user hasn't made public.
When did the Basic Display API stop working?
Meta announced on September 4, 2024 that the Instagram Basic Display API would no longer be available from December 4, 2024, and that all Basic Display requests would fail from that day on. For business and creator use cases, Meta pointed developers to the Instagram API with Instagram Login or with Facebook Login. Nothing was offered for consumer apps, so personal accounts were left without an official API.
In practice, personal-account portfolio feeds lost their data source, feed plugins either moved to the new API or stopped updating, and the 60-day token refresh cron job now refreshes nothing. A grid frozen on late-2024 posts is the usual symptom.
My WordPress Instagram feed stopped working. What now?
Most feed plugins that survived the shutdown now connect through the Instagram API with Instagram Login. That means the account has to be a professional one. The usual fix:
- In the Instagram app, open settings and switch the account to a Creator or Business account. It's free, and you can switch back later from the same menu.
- In your plugin's settings, disconnect the old account and connect it again.
- Clear the plugin's cache so the grid refetches.
Feed plugins and widget services such as Smash Balloon and Behold publish their own reconnect guides, so follow the one for your tool. The hard case is a client who won't convert. No plugin gets around Meta's account-type rule, so use a public-data API and render the posts yourself (PHP example below).
How do I migrate to the Instagram API with Instagram Login?
This is the official migration target and the right choice when you control the account. Here are the real steps:
- Convert the Instagram account to Creator or Business.
- In the Meta App Dashboard, create an app, add the Instagram product, and set up Instagram business login with your redirect URI.
- Request the
instagram_business_basicscope (it replaced the olderbusiness_basicvalue). That covers profile fields and media. - Exchange the short-lived token server-side at
https://graph.instagram.com/access_tokenwithgrant_type=ig_exchange_token. You get a long-lived token valid for 60 days. - Refresh it at
https://graph.instagram.com/refresh_access_tokenwithgrant_type=ig_refresh_token. Meta only allows a refresh once the token is at least 24 hours old, and a token not refreshed within 60 days expires for good.
Access level depends on whose accounts you serve. Standard Access covers professional accounts you own or manage. Serving accounts you don't own needs Advanced Access, which goes through Meta's App Review.
You get first-party data, including reach and story insights no public-data API can see, in exchange for the account-type rule and a token you have to babysit. For the wider comparison, see Instagram Graph API vs scraper API.
Can I embed Instagram posts without an access token?
Yes. Instagram oEmbed is an endpoint that turns a public post URL into embeddable HTML, and since June 2026 it's the lightest official option you have.
For years it needed a Meta app, an access token and App Review for the oEmbed Read feature. On June 15, 2026, Meta announced tokenless access to its oEmbed APIs: you can call the Instagram oEmbed endpoint for public content with no token and no App Review. Token-based integrations keep working, and Meta notes the tokenless rate limits may be lower.
What comes back is thin: html, provider_name, provider_url, type, version and width. No thumbnail or author fields, and no way to list a profile's recent posts, so it can't rebuild a feed. For "show these six posts on a landing page", it's ideal.
What is a public-data API, and when should you use one?
A public-data API is a service that returns what anyone can see on a public Instagram profile as structured JSON, without your users logging in or your app going through Meta review.
It covers what Meta's APIs leave out: personal accounts that won't convert, competitor tracking, or a client portfolio where all you have is the username. You only get what's public. Private accounts, DMs, insights and anything behind a login are out of scope. Profile data is still personal data, so read is scraping public social media data legal before you store or republish it.
Scrape Everything is a REST API for public social media data as clean JSON, covering Instagram and 8 other platforms. It isn't affiliated with Instagram or Meta. These are the Instagram endpoints that matter for a Basic Display replacement:
| Endpoint | What you send | What you get | Credits |
|---|---|---|---|
instagram.profile | username | Bio, avatar, verification and business flags, follower, following and post counts | 1 |
instagram.photos | username, limit (1 to 60, default 12) | Every profile field plus recent posts, newest first | 2 |
instagram.post | url or shortcode | One post, reel or IGTV item | 1 |
instagram.reels | username, limit (1 to 50, default 12) | Recent reels from the profile's Reels tab | 2 |
Full parameter docs are on the Instagram scraper API page, and the free Instagram profile viewer runs the same lookup in your browser.
Two limits matter for feeds. Private accounts return the public subset of profile fields and an empty posts array. And like_count, comment_count and taken_at came back null for every listed post in our tests, so treat null as unknown, show taken_at_text as the date, and use instagram.post (1 credit per post) when you need counts.
Which Instagram Basic Display API alternative fits your use case?
| Use case | Best replacement | Account type needed | Meta review |
|---|---|---|---|
| Your own portfolio feed, account can be Creator/Business | Instagram API with Instagram Login | Business or Creator | No (Standard Access) |
| Client feed, client won't convert or share login | Public-data API (instagram.photos) | Any public account | No |
| Embed a few specific posts | oEmbed | Any public post | No (tokenless since June 2026) |
| Follower count or bio in a profile header | Public-data API (instagram.profile) | Any public account | No |
| Insights, reach, story metrics for your account | Instagram API with Instagram Login | Business or Creator | Depends on permissions |
| App that connects other people's professional accounts | Instagram API with Instagram Login | Business or Creator | Yes (Advanced Access) |
| Monitoring competitors or creators | Public-data API | Any public account | No |
| Private account content | None | n/a | n/a |
Our view: if you own the account and can flip it to Creator, take the official API. It's free and it gives you insights nobody else can. Use a public-data API when the account isn't yours or the owner won't change its type.
How do I get Instagram posts without the Graph API?
Here's a portfolio feed rebuilt on instagram.photos. One POST, a JSON body, a Bearer key, and the base URL https://api.scrapeeverything.com.
- Sign in with Google or GitHub to get 100 free credits. No payment details needed.
- Create an API key in the dashboard and export it as
SCRAPEEVERYTHING_API_KEY. - Call
instagram.photosfrom your server with alimitandcache_days: 1. - Check
is_privatein the response. If it'strue,postswill be empty. - Render the
postsarray in your template.
cURL
curl -X POST https://api.scrapeeverything.com/v1/instagram/photos \
-H "Authorization: Bearer $SCRAPEEVERYTHING_API_KEY" \
-H "Content-Type: application/json" \
-d '{"username": "example_user", "limit": 6, "cache_days": 1}'Response shape, trimmed (illustrative values):
{
"success": true,
"data": {
"id": "1234567890",
"username": "example_user",
"full_name": "Example Studio",
"biography": "Wedding and portrait photography.",
"profile_pic_url": "https://cdn.example/avatar.jpg",
"is_private": false,
"follower_count": 4821,
"post_count": 418,
"posts": [
{
"shortcode": "ABC123xyz_0",
"link": "https://www.instagram.com/p/ABC123xyz_0/",
"type": "photo",
"is_video": false,
"like_count": null,
"comment_count": null,
"caption": "Golden hour at the lake.",
"thumbnail_url": "https://cdn.example/thumb1.jpg",
"taken_at": null,
"taken_at_text": "October 28, 2026"
}
],
"posts_fetched": 6,
"has_more": true
},
"meta": {
"scraper": "instagram.photos",
"cached": false,
"credits_charged": 2
}
}Since instagram.photos returns every profile field too, one call covers both the profile header and the grid.
Node
This runs on Node 18 or later with the built-in fetch:
const API = "https://api.scrapeeverything.com/v1/instagram/photos";
async function getFeed(username) {
const res = await fetch(API, {
method: "POST",
headers: {
Authorization: `Bearer ${process.env.SCRAPEEVERYTHING_API_KEY}`,
"Content-Type": "application/json",
},
body: JSON.stringify({ username, limit: 12, cache_days: 1 }),
});
if (!(res.headers.get("content-type") || "").includes("application/json")) {
throw new Error(`Feed fetch failed: HTTP ${res.status}`); // 502/504 arrive as an HTML page
}
const body = await res.json();
if (!body.success) throw new Error(`Feed fetch failed: ${res.status} ${body.code} ${body.message}`);
return body.data.posts.map((p) => ({
href: p.link,
img: p.thumbnail_url,
caption: p.caption,
type: p.type,
// taken_at (Unix seconds) is usually null in the list; taken_at_text is a readable date
takenAt: p.taken_at ? new Date(p.taken_at * 1000).toISOString() : p.taken_at_text,
likes: p.like_count, // usually null in the list; instagram.post has the count
}));
}
getFeed("example_user").then((posts) => console.log(posts.slice(0, 2)));PHP for WordPress
If your feed lived in a WordPress theme, this replaces the old Basic Display call. The transient means WordPress calls the API at most once an hour, and cache_days: 1 means at most one of those calls per day is billed.
function se_instagram_feed( $username ) {
$cached = get_transient( 'se_ig_' . $username );
if ( false !== $cached ) {
return $cached;
}
$res = wp_remote_post( 'https://api.scrapeeverything.com/v1/instagram/photos', array(
'headers' => array(
'Authorization' => 'Bearer ' . getenv( 'SCRAPEEVERYTHING_API_KEY' ),
'Content-Type' => 'application/json',
),
'body' => wp_json_encode( array( 'username' => $username, 'limit' => 12, 'cache_days' => 1 ) ),
'timeout' => 30,
) );
if ( is_wp_error( $res ) ) {
return array();
}
$body = json_decode( wp_remote_retrieve_body( $res ), true );
$posts = ! empty( $body['success'] ) ? $body['data']['posts'] : array();
set_transient( 'se_ig_' . $username, $posts, HOUR_IN_SECONDS );
return $posts;
}Two things to handle in the template. Null counts first: don't print "0 likes" when the real answer is "unknown". Then thumbnails: URLs from Instagram's CDN expire, so if your pages are cached for weeks, store the images yourself or refresh the feed on a schedule.
Prefer not to write the fetch at all? The same endpoints are available through the MCP server, the CLI (npx scrapeeverything), an n8n node, and the OpenAPI spec at https://scrapeeverything.com/openapi.json.
How much does a daily Instagram feed cost?
instagram.photos costs 2 credits per live call. Add cache_days and we first look for a stored result for the same endpoint and parameters that's at most that many days old. Cache hits cost 0 credits. The caching docs explain the matching: nasa, @nasa and the full profile URL hit the same entry, while a different limit counts as a different request. Cache windows run from 1 to 14 days.
With cache_days: 1, your page can call the API on every render and you still pay for at most one live fetch per account per day. Here's what that costs in credits and on the $19.99 Builder pack (25,000 credits, $0.80 per 1,000):
Setup (instagram.photos) | Credits / 30 days | One Builder pack lasts | Cost per month at Builder rate |
|---|---|---|---|
1 feed, cache_days: 1 | 60 | more than 30 years | about $0.05 |
5 client feeds, cache_days: 1 | 300 | about 83 months | about $0.24 |
10 client feeds, cache_days: 1 | 600 | about 41 months | about $0.48 |
| 1 feed, no cache, 500 page views/day | 30,000 | about 25 days | $23.99 |
Without caching, a modest blog burns credits on reloads alone. Better yet, fetch from a server-side job, not on page render.
Worked example: an agency running 10 client portfolio sites with cache_days: 1 spends 600 credits a month, about $0.48 at the Builder rate. One $19.99 Builder pack (25,000 credits) covers those 10 feeds for about 41 months, and credits never expire. The 100 free credits alone cover one daily feed for about 50 days.
Packs are one-time purchases (see pricing), and the credit calculator runs this math for your numbers. Failures on our side or Instagram's (blocks, timeouts, 5xx errors) are refunded automatically. A username that doesn't exist is a real answer and is billed, so the errors reference is worth a look before you wire up retries.
Refreshing many feeds from one cron job? The free plan allows 60 requests per minute and 5 concurrent requests. Higher limits (300 per minute, 20 concurrent) apply once your total purchases reach $19.99 (any pack).
FAQ
Is the Instagram Basic Display API deprecated or fully shut down?
Fully shut down. Meta set the end-of-life date as December 4, 2024, and said all Basic Display API requests would fail from that day on. There's no reduced mode to fall back to.
Is there an Instagram API for personal accounts now?
Not an official one. Meta's Instagram API with Instagram Login and with Facebook Login both require a professional (Business or Creator) account. If the account has to stay personal and is public, a public-data API is the remaining way to read its profile and recent posts.
Can I still use my old Basic Display access token?
No. Basic Display tokens belong to an API that no longer exists, so requests made with them fail. Connecting the same account through the Instagram API with Instagram Login means a new authorization and a new token with the instagram_business_basic scope.
Can I use Instagram oEmbed without an access token?
Yes, since June 2026. Meta allows tokenless calls to its oEmbed APIs for public content, with no App Review. It's good for embedding specific posts, but it returns embed HTML rather than post data and can't list a profile's recent media.
Does a public-data API work for private Instagram accounts?
No. Scrape Everything only returns public data. A private account returns its public profile fields and an empty posts array, and there's no option to log in on your behalf. For full field details on profile lookups, see how to scrape Instagram profiles with an API or the Instagram profile endpoint.
Is it legal to show another account's public Instagram posts?
It depends on your jurisdiction, what you store and how you use it, and we can't give legal advice. Our guide to scraping public social media data and the law covers the main questions to check first.
Your next step: get 100 free credits, run the cURL call above against the account your widget used to show, and keep cache_days: 1 in the body when you ship it.