Tech Provider Access Verification Stuck in Review?
You don't need to keep waiting on it. Meta retired Tech Provider Access Verification on October 9, 2026: the form and its status field are coming out of the App Dashboard, and endpoints will stop rejecting calls over a missing Access Verification status. Business Verification and App Review for advanced permissions still apply, so confirm those and test whether your API calls actually fail.
If your Tech Provider Access Verification has been "In review" for weeks, you don't need to keep waiting on it. Meta retired Access Verification for Tech Provider apps on October 9, 2026. Business Verification and App Review for advanced permissions still apply, so check those, then test whether your API calls actually fail.
Do I still need Tech Provider Access Verification?
No. Meta no longer requires Tech Provider Access Verification. Meta's October 9, 2026 post on the Meta for Developers blog opens with this line:
"Access Verification will no longer be required in the Tech Provider onboarding flow."
Zoë Lieberman, Meta for Developers blog
Meta's Access Verification doc (updated October 23, 2026) now says the same thing at the top and keeps the old process below it for reference. Here is what the post changes and what it leaves alone:
| What Meta's October 9, 2026 post says | |
|---|---|
| Access Verification form | The form, its prerequisites, and its status field will be removed from the App Dashboard. |
| API calls | Endpoints that rejected calls from businesses without a passing Access Verification status will no longer run that check. |
| Tech Provider status | Adding an app to a business no longer changes the app's business use. An app becomes a Tech Provider when you upgrade it yourself, or through the advanced permissions it requests. Direct Integrator is the default. |
| Business Verification | Still required before your app can access data owned by other businesses. |
| App Review | Still required for advanced permissions, with the same review standards. |
| Data handling | Platform Terms, Developer Policies, Data Use Checkup, the Data Handling Questionnaire, and Data Protection Assessment still apply. |
The post doesn't cover submissions that are already pending, the deadline banners in the App Dashboard, or a date for when the form disappears.
Why is my Tech Provider Access Verification still "In review"?
Meta hasn't explained why pending Access Verification submissions are still showing "In review". The App Dashboard said decisions take about 5 business days, and forum reports describe waits of several weeks with no request for more information.
What developers reported on the Meta Developer Community forum in October 2026:
- Submissions stuck since September. One thread and its replies list submissions from September 19, 21 and 27, 2026, all still "In review" weeks later, with Business Verification already complete.
- App Review approved, Access Verification still pending. Another thread describes a submission from September 23, 2026, App Review approved on October 5, and a dashboard banner saying verification must be completed by 12/9/2026 to avoid restrictions.
- New threads with the same problem. On October 27, 2026, new threads reported a September 29 submission facing a December 16, 2026 deadline, and an October 18 submission past the 5 business days.
The October 18 submission went in nine days after Meta's post, and every one of these was still "In review" after October 9. So the App Dashboard can show a pending status and a deadline banner for a requirement Meta has already retired. Meta hasn't said when the dashboard catches up.
What should I do instead of waiting?
Confirm Business Verification, test your real API calls, and put your effort into App Review. Those are the gates Meta's post says still apply. Here's a checklist:
- Confirm Business Verification. In the App Dashboard, go to Settings > Basic > Verification and check that the app is connected to a verified business. Meta's Business Verification doc says app users from other businesses can't grant permissions to an app until that's done, and all features stay inactive.
- Check whether calls actually fail. Under the legacy process, the check only ran when the person who granted the permission had no role on your app. Once the app has Advanced Access for the permission, test with a token from someone outside your app's roles, such as a client, not your own admin token. If the call returns data, Access Verification isn't blocking you.
- Read the error if one comes back. The legacy check returned error code
100: "Unsupported get request. Object with ID ... does not exist, cannot be loaded due to missing permissions, or does not support this operation." Code100has other causes too, so check the token's granted permissions in the Access Token Debugger before you blame Access Verification. - Focus on App Review for advanced permissions. Advanced Access still goes through App Review, with the same standards. Our Meta app review timeline covers how long a round takes and what makes a submission pass.
- If a deadline banner is still showing, report it with your app ID. Meta's bug tool is the usual route, but forum reports say it answers the "Access verification (tech providers)" product with a note that support moved to the forum. Post there with your app ID, submission date, the banner text, and a link to Meta's October 9, 2026 post, and keep a dated screenshot of the banner.
Which Meta support channels help with a stuck Access Verification?
None of the support channels developers tried could reach the team that handles Access Verification. Every route developers described in the threads we read ended with an automated reply or a pointer back to the forum.
| Channel | What forum reports say happened |
|---|---|
| Business Support AI assistant | Offered a transfer to a human agent, but no case was created. In a Business Verification thread, it said it can't escalate to a live agent. |
| Direct Support cases | In the same Business Verification thread, the AI agent closed one case with a generic "please wait" reply and answered another by pointing back to the forum. |
| Meta Pro Team support | Agents ran diagnostics, found no blockers on the app, and said they have no channel to the verification team. |
| Bug tool | For "Access verification (tech providers)", says support is unavailable for this product and points to the forum. |
| Developer Community forum | Where the reports collect. As of October 27, 2026, none of the threads we read had a reply from Meta staff. |
How does Adeli fit in?
Adeli is a social media and ads API that runs on its own Meta app, so we went through Meta App Review ourselves. When we submitted ads_management, pages_manage_ads and leads_retrieval for App Review, Meta approved all three on the first submission, with the result on October 15, 2026. We followed Meta's instructions for each permission as written: a use-case description where every claim matched the screencast, and a screencast of the full flow.
Adeli covers Meta ads, Instagram and Facebook publishing, and WhatsApp integrations behind one API key. If you're building those features for clients and would rather not run your own review for each permission, start with Adeli's posts API or ads API.