Every week someone in an agency owners' group asks the same thing: "How do I get Instagram API access so I can auto-post for clients?" The honest answer is that the API is very real, very official, and — for most agencies — not something you should build yourself. This post walks the full path so you can make that call with your eyes open: what you need, the two login routes Meta now offers, the App Review gauntlet, how publishing actually works, and the limits nobody mentions until they bite you.
If you're weighing the API against handing over passwords, read Instagram auto posting without password sharing first — this post is the technical follow-up to that one.
What do you need before you can auto-post?
Instagram's content publishing sits inside the Instagram Platform, and Meta gates it behind a specific stack. You need all of these in place before a single post goes out:
- An Instagram professional account — Business or Creator. Personal accounts cannot publish through the API, full stop.
- A Meta app — created at developers.facebook.com, with the Instagram product added and your Privacy Policy and basic settings filled in.
- The right login path and permissions —
instagram_business_basic+instagram_business_content_publishwith Instagram Login, orinstagram_basic+instagram_content_publish+pages_read_engagementwith Facebook Login (more on choosing below). - A Facebook Page — only on the Facebook Login path. Older guides (including the first version of this one) list a linked Page as mandatory. With Instagram Login, Meta's docs now say plainly that the setup does not require a Facebook Page — a real relief for Indian small businesses whose Page was created in 2014 by a nephew and nobody has the login.
- A long-lived access token — obtained via OAuth for each account you publish on behalf of.
Notice the pattern: this is per-account plumbing. Onboard a new client and you repeat the OAuth and connection steps for their account — which is exactly why a good Instagram scheduler exists, so you don't hand-roll this for every brand.
Instagram Login or Facebook Login: which API path should you use?
Meta now offers two configurations of the same platform. For pure auto-posting, Instagram Login is the simpler choice; Facebook Login only earns its extra setup if you need the features in the right-hand column. Per Meta's platform overview and Content Publishing docs:
| Instagram Login | Facebook Login | |
|---|---|---|
| Facebook Page | Not required | Required |
| Publishing permissions | instagram_business_basic, instagram_business_content_publish | instagram_basic, instagram_content_publish, pages_read_engagement |
| API host | graph.instagram.com | graph.facebook.com |
| Publish photos, videos, Reels, carousels, Stories | Yes | Yes |
| Hashtag search, product tagging, partnership ads | No | Yes |
If you only want posts to go out on schedule, pick Instagram Login. If a client sells on Instagram Shopping or runs partnership ads with creators, you'll end up on Facebook Login anyway.
How do you get Instagram API access? The 5 steps
Here's the sequence, in the order Meta actually enforces it:
- Create the app at developers.facebook.com and pick the "Business" type. Fill in Settings → Basic (app name, contact email, and a live Privacy Policy URL — your own site's privacy page is fine).
- Add the Instagram product and choose your login path. With Instagram Login you connect the professional account directly; with Facebook Login you connect the Facebook Page the account is linked to.
- Wire up the OAuth flow so you can capture a short-lived user access token when an account authorises your app. Short-lived Instagram tokens expire in one hour.
- Exchange it for a long-lived token, which lasts 60 days. There is no silent auto-refresh: per Meta's refresh reference, you can only refresh a token that is at least 24 hours old and still unexpired, and the refreshed token is valid for 60 days from that moment. Let it lapse and the client has to log in again.
- Get Advanced Access through App Review and Business Verification — required before you can publish to accounts that aren't yours (next section).
Do you need App Review? Standard vs Advanced Access
This is the question that decides whether you can launch this week or next month. Meta splits access into two levels (source):
- Standard Access — the default. It works for accounts whose users have a role on your app (or on the business portfolio that claimed it). If you're automating your own brand's Instagram, this is enough, and you don't need App Review at all.
- Advanced Access — needed the moment your app serves professional accounts you don't own or manage, used by people with no role on your app. That's every agency-builds-a-tool-for-clients scenario. Advanced Access requires both Meta App Review and Business Verification.
App Review asks you to submit each permission separately, with a screencast demonstrating exactly how your app uses it. Business Verification asks for official documents proving your business's legal name and address — for an Indian agency, have your GST registration or incorporation papers ready and make sure the name matches your Meta business portfolio exactly. In our experience, budget two to four weeks for the pair and at least one round of "please clarify" feedback. If a client asks you to start posting next Monday, the API is not your Monday answer.
How does publishing actually work?
Once you're approved, auto-posting a photo or Reel is a two-step call per post:
- Create a media container —
POST /{ig-user-id}/mediawith the public image or video URL and caption. Meta ingests the media and returns a container ID. - Publish the container —
POST /{ig-user-id}/media_publishwith that container ID. This is the call that puts the post live.
Video and Reels take time to process, so check the container before publishing. Its status_code moves through IN_PROGRESS to FINISHED (ready), or lands on ERROR or EXPIRED (container reference). A carousel adds a step: you create a child container per slide — up to 10 images or videos — then a parent carousel container that references them, then publish the parent. Simple in principle, but it's real backend code you now own, monitor and update every time Meta changes the API.
What are the limits nobody warns you about?
According to Meta's official Content Publishing docs, here are the hard constraints that shape any real scheduling system:
| Limit | What it means |
|---|---|
| 100 posts / 24h | An account can publish max 100 API posts in a rolling 24-hour window. A carousel counts as one post. Check remaining quota via GET /{ig-id}/content_publishing_limit. |
| Containers expire in 24h | A container not published within 24 hours expires. You cannot build containers days ahead — store the post data in your own database and create the container at publish time. |
| Token expiry: 60 days | Long-lived tokens last 60 days and must be refreshed while still valid. Miss the refresh and that account silently stops publishing. |
| JPEG only | JPEG is the only supported image format. PNG exports need converting to JPEG before upload. |
| Carousels: 10 items | Up to 10 images, videos or a mix, all cropped to the first item's aspect ratio (1:1 by default). |
| No shopping tags or filters | The API can't add shopping tags or Instagram filters — posts that need them still go out by hand. |
| Media hosting | Images and videos must be served from a publicly reachable URL Meta can fetch — so you need your own storage/CDN too. |
That container-expiry rule is the one that quietly kills naive "schedule it and forget it" builds. Real scheduling means running your own clock and firing the container-plus-publish sequence at the scheduled minute — not pre-baking posts for the month. The same docs also list newer options worth knowing: an alt_text field for image posts and trial Reels (trial_params) that are shown to non-followers first — useful context if you're scheduling Reels in advance.
Should you build this yourself?
For an agency, almost never. Getting API access is the easy part; the ongoing tax is what hurts — per-client OAuth, token-refresh monitoring, container timing, retries when Meta hiccups, and re-approval whenever the API shifts. That's an engineering function, not a marketing one. Unless you're a software company, every hour spent on this is an hour not spent on client content.
| Build on the API yourself | Use a tool with approved access | |
|---|---|---|
| Time to first client post | Weeks (App Review + Business Verification) | Same day — client connects once |
| Who handles token refresh | Your code, forever | The tool |
| Who absorbs API changes | Your developer | The tool |
| Makes sense when | You're building a product, or need custom integrations | You're an agency shipping client content |
The practical route is to use a tool that already holds approved API access and manages tokens for you — you connect a client's account once and schedule normally.

That's the entire reason our Instagram scheduler exists: the API plumbing is done, so a solo operator in Jaipur or a 10-person team in Mumbai gets the same official auto-publishing without a developer on payroll. If you're evaluating where publishing fits alongside approvals, reporting and billing, the agency management software overview lays out the full loop.
FAQ
Do I need a Business account to use the Instagram API for posting?
Yes. Auto-posting requires an Instagram professional account, either Business or Creator. A personal account cannot publish through the API. Switch the account to professional in Instagram's settings, connect it to your Meta app, and request the instagram_business_content_publish permission (or instagram_content_publish on the Facebook Login path).
Do I need a Facebook Page to use the Instagram API?
Not any more. With the Instagram API with Instagram Login, Meta's documentation says no Facebook Page needs to be linked to the professional account. You only need a Page if you choose the Facebook Login path, which you would pick for hashtag search, product tagging or partnership ads.
How long does Instagram API app review take?
Plan for two to four weeks in practice. Each permission is reviewed separately and needs a screencast showing real usage, and Advanced Access also requires Business Verification with official documents. You only need this to publish to accounts you don't own; your own accounts work with Standard Access.
How many posts can the Instagram API publish per day?
Each account is limited to 100 API-published posts in a rolling 24-hour window, and a carousel counts as a single post. Query the content_publishing_limit endpoint before publishing to see how much quota remains. No agency running a normal brand calendar comes anywhere close to this limit.
How long does an Instagram API access token last?
A short-lived token lasts one hour; exchange it for a long-lived token that lasts 60 days. You can refresh a long-lived token once it is at least 24 hours old and still valid, which gives another 60 days. An expired token cannot be refreshed, so the account must log in again.
Skip the API build — just schedule
Connect each client's Instagram once and auto-publish through Meta's official API on your calendar. No password sharing, no token code. Founding pricing from ₹999/month, with a 7-day money-back guarantee.