Instagram Basic Display API (Deprecated): What Replaced It in 2026?

The Instagram Basic Display API is no longer available. If you are searching for it in 2026, the real question is not what it used to do. The real question is what replaced it, which migration path fits your use case, and what to do if you still need Instagram profile or media data today. In most cases, the replacement path now points to newer Instagram API models for professional accounts, while some older Basic Display use cases need a different workaround depending on whether you are building a website feed, a creator tool, or a business product. If you need a broader view of Instagram’s current API ecosystem before going deeper, start with [What Is the Instagram API? A Beginner’s Guide (2026)].

This is why a useful guide should not start with history. It should start with the current answer. The Instagram Basic Display API belongs to Instagram’s older access model, and Meta’s current direction now centers on newer Instagram API paths, especially for professional account workflows. If your old setup broke after the shutdown, this guide will help you decide what to use next and what to stop trying to rebuild.

Is the Instagram Basic Display API still available?

No. The Instagram Basic Display API is no longer available for normal use in 2026. If you are still searching for it, you are usually dealing with one of three situations: an older app that needs migration, a website or plugin that used Basic Display before the shutdown, or a developer trying to understand which current Instagram API should replace it.

That distinction matters because not every searcher has the same problem. Some people need a new professional account workflow. Others only want to keep an Instagram feed visible on a website. Others are maintaining a product that depended on an older token flow and now needs a new access model. So before you look for a “replacement,” you first need to know what type of Instagram data access your workflow actually needs.

The data it could return included:

• Username — the account's Instagram handle

• Account type — Personal, Business, or Creator

• Media count — total number of posts

• Profile picture URL

• Individual media objects — photos, videos, and albums

• Media fields — ID, caption, media type, media URL, thumbnail URL, permalink, and timestamp

• Media children — for carousel posts, the individual media items within an album

What it explicitly could not do was equally important: it had no access to follower counts, following lists, engagement metrics, story content, insights data, or any ability to post or publish content. It was read-only, lightweight, and deliberately scoped to the minimum data needed to display someone's feed.

What replaced the Instagram Basic Display API?

For many professional account use cases, the main replacement path now leads to Instagram API with Instagram Login.

Meta’s current documentation positions this as a simpler onboarding path for Instagram professional accounts, especially for apps that need account management, publishing, moderation, messaging, or insights without relying on the older Facebook Page-heavy setup. That does not mean it is a perfect one-to-one replacement for every Basic Display use case. It means the Instagram API ecosystem has moved forward, and developers now need to choose the current path based on account type and workflow rather than trying to rebuild the old model exactly.

If your real goal is business-facing Instagram account data rather than simple media display, [Instagram Business Discovery API: What Can You Actually Get?] is one of the most useful next reads, because it explains what current business and creator workflows can access now.

The Instagram Graph API — for Business and Creator accounts, with powerful features for content management, analytics, messaging, and commerce, but with strict app review requirements and account type restrictions.

The Instagram Basic Display API — for personal and consumer-facing use cases, with narrow read-only access and a simplified OAuth flow that didn't require linking a Facebook Page.

The Basic Display API launched in October 2019 and represented a genuine step forward in terms of privacy-conscious API design. By separating profile and media permissions into distinct scopes, removing location data and follower counts from the available fields, and requiring explicit user authorization through OAuth, it gave developers a legitimate path to consumer integrations without exposing sensitive social graph data.

For the next five years, it powered an enormous ecosystem of Instagram feed plugins, website integrations, portfolio display tools, and lightweight social media apps. Hundreds of WordPress plugins — Smash Balloon, Spotlight, LightWidget, SnapWidget, and many others — ran their personal account integrations entirely on the Basic Display API. Millions of websites displayed live Instagram feeds thanks to it.

Then Meta announced its end.

If you specifically want to understand the newer access model, read [Instagram API with Instagram Login: What It Replaces and Who Should Use It].

Who needs to migrate and who does not?

Not everyone searching this keyword needs the same fix.

If you are maintaining an older app that depended on Basic Display tokens and media access, you need a migration decision now. If you only want to show an Instagram feed on a website, your real problem may be plugin compatibility or content display strategy rather than a full API migration. If you are building a professional product for creators, marketers, or businesses, then the correct next step is usually to evaluate current Instagram API options based on account type, permissions, and the workflow your product actually supports.

That is the key change in 2026. The question is no longer “How do I keep using Basic Display?” The question is “Which current Instagram API path fits what I am trying to build?”

If your team is replacing an older setup and needs a practical migration path, see [Instagram Basic Display API Migration: What to Change, What to Keep, and What to Drop].

Which migration path fits your use case?

Different use cases now lead to different answers.

If you need professional account access

Start by evaluating Instagram API with Instagram Login. Meta’s current direction makes this the clearest path for many professional account workflows, especially if your product needs profile access, publishing, moderation, messaging, or insights.

If you need publishing, moderation, or insights

Do not think in terms of a “Basic Display replacement” alone. Instead, map your product workflow to the current Instagram API product family and required permissions. In many cases, this is a broader decision than simply swapping one endpoint for another.

If your product also depends on account-level competitive data or business profile lookups, [Instagram Business Discovery API: What Can You Actually Get?] gives you a more practical picture of where Instagram access has moved.

If you only need an Instagram feed on your website

Your real issue may be front-end content display after the Basic Display shutdown, not a full API migration. In that case, you should compare embed-based, cached, or service-based approaches rather than trying to recreate the old Basic Display flow exactly as it was.

If you are maintaining an old plugin or app

Audit every dependency that still assumes Basic Display endpoints, long-lived tokens, or older login behavior. Then decide whether you should migrate, replace the plugin, rebuild the feature on a newer API model, or simplify the feature entirely.

Instagram API with Instagram Login vs older Instagram access models

This is where many teams get confused. They assume the new path is simply the old path with a new name. It is not.

Instagram API with Instagram Login is part of Meta’s newer direction for Instagram professional accounts. The onboarding path is simpler than older Facebook-dependent setups, and it is designed for current professional account management workflows. That makes it more useful for real business and creator products than the old Basic Display model ever was.

But that also means you should stop evaluating it as if the goal were to preserve the old behavior exactly. A website feed, a professional dashboard, a content publishing tool, and a creator analytics product are not the same use case. The correct migration choice depends on what the product actually does.

If you are also working on follower-related access, audience growth, or account-level tracking, these two pages help connect the old Basic Display mindset to current Instagram data workflows:

- [Instagram Graph API: Retrieve Followers and Following (2026)]

- [Instagram API Follower Count Guide]

Which migration path fits your use case?

Which migration path fits your use case?

Different use cases now lead to different answers.

If you need professional account access

Start by evaluating Instagram API with Instagram Login. Meta’s current direction makes this the clearest path for many professional account workflows, especially if your product needs profile access, publishing, moderation, messaging, or insights.

If you need publishing, moderation, or insights

Do not think in terms of a “Basic Display replacement” alone. Instead, map your product workflow to the current Instagram API product family and required permissions. In many cases, this is a broader decision than simply swapping one endpoint for another.

If your product also depends on account-level competitive data or business profile lookups, [Instagram Business Discovery API: What Can You Actually Get?] gives you a more practical picture of where Instagram access has moved.

If you only need an Instagram feed on your website

Your real issue may be front-end content display after the Basic Display shutdown, not a full API migration. In that case, you should compare embed-based, cached, or service-based approaches rather than trying to recreate the old Basic Display flow exactly as it was.

If you are maintaining an old plugin or app

Audit every dependency that still assumes Basic Display endpoints, long-lived tokens, or older login behavior. Then decide whether you should migrate, replace the plugin, rebuild the feature on a newer API model, or simplify the feature entirely.

Instagram API with Instagram Login vs older Instagram access models

This is where many teams get confused. They assume the new path is simply the old path with a new name. It is not.

Instagram API with Instagram Login is part of Meta’s newer direction for Instagram professional accounts. The onboarding path is simpler than older Facebook-dependent setups, and it is designed for current professional account management workflows. That makes it more useful for real business and creator products than the old Basic Display model ever was.

But that also means you should stop evaluating it as if the goal were to preserve the old behavior exactly. A website feed, a professional dashboard, a content publishing tool, and a creator analytics product are not the same use case. The correct migration choice depends on what the product actually does.

If you are also working on follower-related access, audience growth, or account-level tracking, these two pages help connect the old Basic Display mindset to current Instagram data workflows:

- [Instagram Graph API: Retrieve Followers and Following (2026)]

- [Instagram API Follower Count Guide]

Instagram API with Instagram Login vs older Instagram access models

The Basic Display API shutdown had different impacts depending on account type and use case:

Personal Instagram Account Holders: Websites and apps that connected a personal Instagram account to display a live feed — the most common use case — stopped working entirely. The only path forward is converting the account to a Creator or Business account to use the Instagram Graph API instead.

Business and Creator Account Holders: Largely unaffected. These accounts were already using the Instagram Graph API (not the Basic Display API), which continues to function and was not impacted by the deprecation.

WordPress Plugin Users (Smash Balloon, Spotlight, LightWidget, SnapWidget, etc.): Plugins that handled personal account connections through the Basic Display API required users to reconnect their accounts using a new connection method after converting to a professional account type.

Custom Developer Integrations: Any application built on the Basic Display API's endpoints needed a full migration to the Instagram API with Instagram Login or the Instagram Graph API. This involved reconfiguring app settings, updating OAuth flows, swapping deprecated scopes, and modifying API endpoint URLs and response handling.

Analytics and Social Media Tools: Products that offered Instagram feed embedding or profile monitoring for personal accounts had to either add account conversion flows for their users or discontinue those features.

Common migration mistakes after the Basic Display API shutdown

The most common mistake is assuming there is a perfect one-to-one replacement. In practice, the current Instagram API ecosystem is more segmented.

The second mistake is treating all use cases as identical. A website feed, a creator analytics tool, and a business publishing workflow do not need the same migration path.

The third mistake is focusing too much on historical endpoints and not enough on the current problem. Historical reference is useful, but it should not sit above the migration answer.

The fourth mistake is trying to rebuild old plugin behavior without checking whether the original use case still deserves an API-based solution at all.

A fifth mistake is skipping the current Instagram product map entirely. That is why it helps to read [What Is the Instagram API? A Beginner’s Guide (2026)] before making a migration decision based only on one deprecated keyword.

Historical note: what the Instagram Basic Display API used to do

The Instagram Basic Display API was designed to let apps access basic profile information, photos, and videos from Instagram accounts under the older access model. For a while, it became a common option for lightweight display use cases, especially website feeds, personal content pulls, and simple media integrations.

That historical role is still useful to understand, because it explains why so many older tutorials, plugins, and small products still reference it. But in 2026, that role is no longer the main thing users need from this page. The practical question is replacement, not nostalgia.

If you keep this section, keep it short. It should explain the old role of the API without dragging the user through endpoint history before they get an answer.

Historical note: what the Instagram Basic Display API used to do

If you're maintaining a legacy integration built on the Basic Display API, here is the correct migration path:

Step 1: Assess Your Use Case

Determine whether you need:

Basic profile and media display → Instagram API with Instagram Login is sufficient

• Analytics, insights, publishing, messaging, or commerce → Instagram Graph API is required

• Multi-account management for clients → Instagram Graph API with Facebook Login for Business

Step 2: Convert Personal Accounts to Professional

Since no public Meta API supports personal Instagram accounts anymore, any users with personal accounts who need API-connected functionality must convert to a Creator or Business account. This conversion is free and reversible, and it doesn't require having a business — the Creator account type is designed for individual content creators and functions equivalently to personal accounts for most content purposes.

Step 3: Configure Your Meta App

In the Meta for Developers dashboard:

• Update your app type settings to support Instagram API with Instagram Login or Instagram Graph API as appropriate

• Request the correct updated permissions/scopes for your use case

• Remove any references to deprecated Basic Display API products from your app configuration

• Add your updated OAuth redirect URIs

Step 4: Update Your OAuth Flow

Replace the old authorization endpoint (https://api.instagram.com/oauth/authorize) with the new Instagram Login authorization endpoint. Update the scope parameters — the old instagram_graph_user_profile and instagram_graph_user_media values are deprecated. Use the new scope values appropriate to your API choice.

Step 5: Update Your API Endpoints

Replace old Basic Display API endpoint calls:

Step 6: Submit for App Review (If Needed)

Apps that allow external users (not just the app developer) to authenticate and grant data access must pass Meta's App Review. This involves providing detailed documentation of your use case, a privacy policy, and — for some permissions — screen recordings demonstrating how your app works. Apps used only in development mode by testers can bypass this step for initial testing.

Step 7: Test Token Refresh Logic

Long-lived tokens under the new API still expire after 60 days without renewal. Ensure your application's token refresh logic is updated to use the correct refresh endpoints and handles token expiry gracefully.

Common Errors After the Basic Display API Deprecation

If you or your users are seeing errors in Instagram integrations post-deprecation, here are the most common causes and what they mean:

"This app is not authorized to access this endpoint" — The app is attempting to call Basic Display API endpoints that no longer exist. Full migration to the new API is required.

"Session invalid" or "400 Session Invalid" — Access tokens generated through the old Basic Display API flow are no longer valid. Users need to re-authenticate through the new flow.

"Account type not supported" — The connected account is a personal account, which is no longer supported by any Meta API. The user needs to convert to a Creator or Business account before reconnecting.

"Scope not valid" — The app is requesting deprecated OAuth scopes (user_profile, user_media). These must be updated to the new scope values.

Feed not updating / showing cached images only — The widget or plugin lost API access at the December 2024 deprecation. The account must be reconnected through the new authentication method.

Key Limitations That Remain in 2026

Even after migrating successfully, it's important to understand what the current Instagram API ecosystem still does not support:

• Personal account access — There is no official path. Any tool that claims to pull data from personal accounts without user authentication is using unofficial methods that violate Meta's Terms of Service.

• Follower and following lists — The Graph API does not expose follower or following data through standard permissions. There is no official way to retrieve a list of an account's followers programmatically.

• Competitor analytics — You can only access data from accounts that have explicitly authorized your application. Public competitor account data is not available through official APIs.

• Stories without special permissions — Story content requires specific Instagram permissions that must be explicitly requested and approved through App Review.

• Arbitrary public account scraping — You cannot fetch data from any public Instagram account you choose. All Graph API data access is scoped to authorized accounts only.

FAQ

Is the Instagram Basic Display API still available in 2026? No. The Instagram Basic Display API was permanently shut down on December 4, 2024. All requests to its endpoints now return errors. It is no longer available under any circumstances.

Can I still embed my personal Instagram feed on my website? Not using official Meta APIs. To embed an Instagram feed using official integrations, you must convert your account to a Creator or Business account and use the Instagram Graph API or Instagram API with Instagram Login. Feed display plugins updated for post-deprecation (like Smash Balloon, Spotlight, LightWidget) support this new flow.

What is the Instagram API with Instagram Login and how is it different from the Basic Display API? The Instagram API with Instagram Login is the functional successor designed for consumer-facing apps that need basic profile and media access. The key difference is that it only supports Professional accounts (Business or Creator) — personal accounts are no longer supported. The OAuth flow is similar in simplicity but uses updated scopes and endpoints, and requires the account to be a professional type.

Do I need a Facebook Page to use the new Instagram API? Not necessarily. The Instagram API with Instagram Login allows authentication without a Facebook Page, which is similar to how the Basic Display API worked. The Instagram Graph API via Facebook Login for Business does require a Facebook Page connection. The right choice depends on your use case.

Will Meta release a new API for personal Instagram accounts? There is no current indication from Meta that a new consumer-facing personal account API is planned. Meta's developer strategy clearly prioritizes Business and Creator accounts. Brands and individuals using Instagram for professional purposes should convert to professional account types.

What happened to my Instagram widget / plugin after December 2024? If your plugin used the Basic Display API to connect a personal account, it stopped pulling new content on December 4, 2024. Most major Instagram feed plugins have since updated to support the new authentication method. You need to convert your Instagram account to a Creator or Business type and reconnect it in your plugin's settings.