How Long Does Meta App Review Take? Now 20 Days
The short answer
Meta app review now takes up to 20 business days per submission, by Meta's own estimate. When we checked on November 4, 2026, Meta's estimate had moved from 10 business days to 20. Getting a full set of Instagram API permissions approved usually takes weeks to a couple of months, because each rejection sends a permission back for another round, and resubmitting is the slow part.
How long does Meta app review take?
As of November 4, 2026, Meta estimates up to 20 business days for a review decision, double the 10 business days it showed before. That covers one round: you submit, a reviewer tests your app, and you get an approval or a rejection for each permission. Meta's older submission guide still says "you should receive a decision within a week," so plan around the newer, longer estimate.
When we went through Meta's reviews for Instagram permissions while working with a couple of clients, each round took roughly 8 to 10 days to come back, before Meta doubled its estimate. There was a lot of back-and-forth with Meta support between rounds, and a full set of permissions took several rounds.
| What you're timing | What to expect |
|---|---|
| One review round (Meta's estimate, November 2026) | Up to 20 business days (was 10) |
| One review round (our experience, before November 2026) | Roughly 8 to 10 days |
| Fixing a rejection before resubmitting | Days, depending on whether you re-record the screencast |
| A full set of Instagram permissions, with rejections | Weeks to a couple of months |
| Ads permissions, first submission (our experience) | Approved in one round |
Plan around the last row. A 20-business-day decision only saves time when it's an approval.
Ads permissions went through faster for us. Our submission for ads_management, pages_manage_ads, and leads_retrieval was approved for all three on the first try, with the decision arriving on October 15, 2026. Each use case only claimed what its screencast showed, and the screencast ran the whole flow from login to a paused campaign.
What does Meta review before an app goes live?
Meta runs two separate reviews, and each has its own wait. Neither has a predictable timeline, and they can overlap or block each other.
| What gets reviewed | When you need it | What it asks for | Wait time |
|---|---|---|---|
| Business Verification | Your app requests Advanced Access, or lets other businesses access their own data | Proof that your business is a real, registered entity | Varies, unpredictable |
| App Review | Every permission that needs Advanced Access | A written use case and a screencast for each permission | Varies, unpredictable |
If you build a product that lets customers connect their own Instagram accounts, expect to go through both.
Updated October 19, 2026: Meta retired Tech Provider Access Verification on October 9, 2026, so it's no longer a separate step, but Business Verification and App Review still apply.
Why does Meta app review take so long?
Meta app review takes a long time mostly because of rejection loops, more than the queue itself. A few things stack up:
- Permissions are judged one by one. A single submission can come back half approved, and the rejected permissions go into the next round.
- A rejection costs a full round. You fix the problem, resubmit, and wait again.
- Rework happens between rounds. Re-recording a screencast or rewriting a use case takes days. Sometimes the product has to change before the video can show the feature.
- Feedback is generic. Meta's rejection notes tend to be a template with a policy link, so it can take a support exchange to find out which part failed.
- More apps are in the queue. In our experience, a surge of vibe-coded apps, vertical AI companies, and AI content-generation tools requesting Instagram access has made review slower than it used to be.
If you're blocked on this, an API that already holds the approvals, like Adeli's Instagram API, takes the review off your roadmap.
What is the Meta app review process?
The Meta app review process has four stages: build the feature, clear the account-level requirements, submit each permission, and wait for a decision per permission.
- Build the feature first. Meta asks you to "make at least 1 successful API call using each permission" before requesting it, within 30 days of submitting.
- Clear the account-level gates. Complete Basic Settings (icon, category, privacy policy URL), add a data deletion URL or callback, and finish Business Verification if you need Advanced Access. No registered company? See Meta business verification for individual developers.
- Submit each permission. Each one gets its own written description and its own screencast.
- Get a decision per permission. Approved permissions go live. Rejected ones need a fix and another round.
The same process covers Facebook Page permissions such as pages_manage_posts. Our Facebook Graph API guide walks through which ones a posting app needs.
What are the Meta app review requirements for Instagram?
To publish to Instagram professional accounts your customers own, your app needs Advanced Access, and Advanced Access requires Meta app review. The Instagram App Review docs ask apps that serve multiple businesses for "a screencast showing the end-to-end user experience for that specific permission or feature." Request only the permissions your product uses: the Instagram API permissions guide lists each one and what it unlocks.
| Requirement | What it means in practice |
|---|---|
| Advanced Access | Required if your app serves accounts you don't own or manage |
| Business Verification | Required for Advanced Access |
| One successful API call per permission | The feature has to work before you ask for it |
| Privacy policy and data deletion | Live URLs that cover the data each permission touches |
| A reviewer-accessible app | "Your app must be publicly available," with a working test path |
| A test account with real content | An Instagram professional account with posts, and followers if you request insights |
| Data handling questions | Every data processor that touches Meta data, and the countries each one uses. How to answer them |
Instagram also has two sets of permissions, and each set is reviewed separately. Request the one your users will actually log in with:
- Instagram API with Instagram Login. Uses permissions like
instagram_business_basicandinstagram_business_content_publish. - Instagram API with Facebook Login. Uses
instagram_basic,instagram_content_publish, and Facebook Page permissions such aspages_show_list.
How do I answer Meta's data handling questions about processors?
List each service that touches the data you get from Meta, pick its service category, and select the countries it documents publicly. Meta asks these data handling questions of every app that is live with a use case or has Advanced Access.
The processor part has three questions for each service you add:
| Meta's question | What to put |
|---|---|
| Which processors or service providers will have access to Platform Data? | Every outside service that stores or reads it (hosting, database, analytics, error tracking), plus your own companies |
| Which category of services? | One or more of: analytics and measurements, advertising, goods and services, IT solutions and cloud storage, research, legal, other |
| Which countries will it process the data in? | Every country it documents, including countries where staff can access the data remotely |
Meta defines Platform Data as "any data that you receive from Meta," such as user IDs, email addresses, and access tokens. If a service never sees that data, it doesn't belong on the list.
To find the countries, go to each provider's own documents. That's how we answered ours:
- Privacy policy. Most vendors name the countries where they process data. Meta's own question notes that "many data processors and service providers provide this information on their corporate website."
- Subprocessor list. Hosting and database providers usually publish one, with a location for each subprocessor.
- Data Processing Agreement (DPA). If the public pages are vague, ask the vendor for its DPA. Ours sent theirs without any fuss.
What if your provider doesn't publish every location? The form has no "Global" or "Unknown" option, so select every country you can document and leave it there. Don't hold your submission for a perfect list. You've already told Meta who the processor is, and in our experience Meta wants a good-faith answer based on what that processor publishes. It doesn't need an exhaustive one. Meta does recommend checking your answers with legal or data handling experts, so do that if you have them.
The same section asks for the legal entity responsible for the data and its country, and about any national security requests from public authorities. Those are about your own company, so you can answer them without asking any vendor.
What rejections should I expect from Meta app review?
Expect at least one rejection. We hit each of these when we went through Meta's reviews for clients:
- Screencast gaps. Meta can accept your use case and still reject the permission because the video skips a step. It needs to show the complete login, the user granting the permission on the consent screen, and the feature working end to end.
- A use case not tied to a feature. If the description doesn't say which feature needs the permission, how the integration works, and how it helps the end user, Meta can reject it as not needed for your app's core functionality.
- A rewrite that reopens an accepted use case. If Meta accepted the use case and only the video failed, keep the text and fix the video. Rewritten text is judged again, and it can fail on grounds that passed last time.
What should my Meta app review video show?
Your Meta app review video should show one user going from logged out to the feature working, in one take, for that specific permission. Meta's screen recording guidance asks you to "record in high-resolution, 1080 or better" and to "use English as the app UI language," with captions or tooltips for any button whose purpose isn't obvious.
A screencast that passes usually covers:
- Signing in to your app.
- Starting the Instagram connection and completing Meta's login.
- The consent screen, with the permission being granted.
- The feature doing its job, with the result visible (for publishing, the post live on Instagram).
- Nothing the description doesn't claim, and everything it does.
Some permissions carry extra rules. For comment management, Meta's review instructions ask to see the account respond to a new comment within 30 seconds, so record that in one unbroken take.
How to pass Meta app review for instagram_business_content_publish
To pass review for instagram_business_content_publish, show a post being created in your app and then appearing live on the connected Instagram account. Meta describes the permission as letting an app "create organic feed photo and video posts on behalf of a business user."
- Show the whole path. Log in, grant access, compose, pick the account, publish, then cut to the post on Instagram.
- Claim only what you publish. If the description says carousels, the reviewer may look for one.
Is there a faster way to get Instagram API access?
Yes. Use an API that already owns an approved Meta developer app. Adeli maintains the developer app on every supported network, completes each platform's review process, and manages OAuth connections and token refresh.
- One API key. Your team holds one key instead of one relationship per platform.
- Your users' own accounts. Each user connects their own Instagram account through Adeli.
- Every network in one call. Adeli publishes to Instagram, TikTok, YouTube, Facebook, X, and Bluesky through the same posting API, and Facebook Pages work the same way on the Facebook API.
You can get started for free.