Meta Tech Provider Access Verification: Complete 2026 Guide

Tech Provider Access Verification is the check Meta runs on any business that has created or claimed a Meta app and wants that app used by other businesses to reach their data. If your app calls permissions like business_management, instagram_basic, leads_retrieval or whatsapp_business_management on behalf of clients, your business has to pass this check before those calls will work for anyone who isn't already a named user on the app itself.

I run Meta App Review and Tech Provider approvals full-time through Mojo Web Technology, and Access Verification is one of the steps clients ask me about most — mostly because Meta's own documentation spreads it across several pages that use similar-sounding names. This guide pulls all of that into one place: what it is, why it exists, who actually needs it, when Meta introduced it, how long it realistically takes, and exactly what the form asks, field by field.

What Is Tech Provider Access Verification?

Tech Provider Access Verification is the process Meta uses to confirm that a business operates as a genuine Tech Provider — a business with a legitimate need to access data owned by other businesses in order to provide those businesses a service. If your business is verified, apps it claims can be used by other businesses. If it isn't, Meta's API rejects those calls with an error, even if the underlying permission itself has Advanced Access.

Tech Provider, Business Verification, App Review, and Access Verification Are Four Different Things

This is where most of the confusion comes from, because all four sound like variations of "getting approved." They're actually separate steps that check different things:

• Business Verification confirms your business's identity — name, address, phone, website — with Meta.
• App Review approves specific permissions (like whatsapp_business_management or instagram_basic) for your app, based on how you say you'll use them.
• Tech Provider Access Verification checks the business that claimed the app, not the permission itself — it confirms that business is entitled to use client data at all.
• Embedded Signup is the onboarding flow your clients go through to connect their own WhatsApp Business Account to your app once you're set up as a Tech Provider.

Meta's documentation states this directly: "Note that access verification is independent of App Review, so each of the permissions below must still be approved for Advanced Access before a non-role user can grant them to an app." In practice that means passing Access Verification doesn't skip App Review, and passing App Review doesn't skip Access Verification — for a new business, Meta requires Business Verification and an App Review submission before you're even able to complete the access verification step.

Why Is Tech Provider Access Verification Required?

Meta introduced this check to stop apps from pulling business data — ad accounts, Page insights, leads, catalogs, WhatsApp messaging assets — on behalf of companies that have no real relationship to that business. Before this existed, an app claimed by any business could, in theory, request access to another business's assets through the same permission grant flow a legitimate agency or SaaS platform would use. Access Verification adds a business-level check on top of the permission-level check App Review already does.

Who Needs to Complete Tech Provider Access Verification?

Any business that has created or claimed an app that other businesses will use, and that needs one of the following permissions, must be verified as a Tech Provider before those other businesses can use the app:

• ads_management, ads_read, attribution_read
• business_management, catalog_management
• instagram_basic, instagram_business_basic, instagram_business_content_publish, instagram_content_publish, instagram_creator_marketplace_discovery, instagram_manage_insights
• leads_retrieval, manage_app_solution, page_events
• pages_manage_ads, pages_manage_cta, pages_manage_engagement, pages_manage_instant_articles, pages_manage_posts, pages_read_engagement, pages_read_user_content, pages_show_list, pages_utility_messaging
• publish_video, read_insights
• threads_basic, threads_content_publish, threads_keyword_search, threads_manage_insights, threads_manage_mentions, threads_manage_replies, threads_read_replies
• whatsapp_business_management
• facebook_creator_marketplace_discovery

If the person granting the permission already has a role on the app itself, Meta skips the business-level check entirely. Access Verification only kicks in when someone outside the app's own team — a client, in most agency and SaaS setups — is the one granting access.

When Did Tech Provider Access Verification Start?

Meta introduced Access Verification on June 2, 2022, rolling it out to eligible businesses in monthly waves rather than all at once. Existing businesses that had already been granted Advanced Access to the affected permissions were given 60 days from their notification email to complete the process. If a business didn't complete it in that window, Meta began gradually subjecting their API calls to the verification check rather than cutting them off all at once.

What the Access Verification Form Actually Asks

Once you start the process — either from the link in Meta's notification email or from Basics > Verifications > Access verification in the App Dashboard — any Admin on the business account fills out a short form. Here's exactly what it asks, field by field, based on the live form on my own account for Mojo Web Technology:

1. Which options best describe your business? — checkboxes for Agency, Freelancer, Consultancy, SaaS Platform, or Other. If your business runs multiple brands, Meta asks you to pick the option that matches the part of the business acting as the Tech Provider.
2. How will your business use Platform Data to enable a product or service on behalf of your clients? — a free-text field. Meta's own instruction here is to keep it short and skip technical jargon. On my form I wrote: "We are just using API to fetch live data and display. Mostly insights and statistics to improve our performance and growth." That's the level of plain-language detail Meta is looking for — what data you pull and what you actually do with it for the client.
3. Does your business manage multiple business portfolios? — a Yes/No question. Answering Yes means you'll be asked for the specific Business Portfolio IDs you manage.
4. Provide a link to your website — Meta is explicit that this needs to be a complete, working site that shows the service you just described and identifies the business providing it. A landing page with no explanation of what you do, or a broken/placeholder URL, is a common reason this step stalls.

How Long Does Tech Provider Access Verification Take?

Meta's own documentation gives one clear number for its side of the process: "once a business admin has completed the process a decision will be made within approximately 5 days." Meta's 2022 announcement of the program describes the same figure as "typically five business days." That's the timeline for Meta's decision once a complete form has been submitted — it isn't a guarantee, and Meta doesn't commit to it as a hard SLA.

Three timelines get mixed together when people ask "how long does this take", and they're worth separating:

• Business Verification — a separate, prerequisite process with its own timeline; it has to be done and approved first.
• Meta's Access Verification decision — approximately 5 business days after a complete form is submitted, per Meta's documentation.
• Existing businesses given a 60-day compliance window — the deadline Meta sets before an unverified business's API calls start failing.

Where I can actually speak to speed is the part I control: preparing and submitting the form itself. I've personally taken more than 20 businesses through Tech Provider Access Verification, and when I'm handling the submission — answering the Platform Data question in the right amount of detail, making sure the website matches the description, checking Business Verification and account standing first — the form itself is ready to submit within 1–2 days. Meta's own review of a complete, well-matched submission then typically follows within that roughly 5-business-day window they publish.

What Happens If Access Verification Is Rejected?

If Meta denies Tech Provider verification, business admins get a rejection email and app admins get a rejection developer alert. From that point, any API call that needs one of the listed permissions fails for every user who doesn't have a role on the app itself — the permission's Advanced Access approval doesn't matter if the business behind the app isn't verified. You can go through the process again if your use case has changed since the rejection.

Can a Verified Tech Provider Lose Its Status?

Yes. Meta treats a previously verified business as unverified again if any of these happen:

• The business's own verification status changes to unverified.
• The app becomes disconnected from the business that created or claimed it.
• The business account becomes restricted.

Once whichever condition caused this is reversed, the business is automatically considered a verified Tech Provider again — there's no separate re-application needed for that specific case.

Access Verification vs. the WhatsApp "Become a Tech Provider" Flow

If you're specifically building on the WhatsApp Business Platform, Meta also documents a dedicated onboarding path: from the App Dashboard, go to Use Cases > Customize (the pencil icon) on the WhatsApp use case, then choose Tech Provider onboarding from the side menu. That page walks through two steps — verifying your business (the same Business Verification described above), then App Review, which covers reviewing your app settings, recording and submitting videos of your app in action, and submitting supporting documentation. If you're onboarding jointly with a Solution Partner rather than independently, you'll need their app ID for this flow.

This WhatsApp-specific onboarding and the general Access Verification form described earlier both exist in Meta's current documentation and cover overlapping ground — Business Verification plus a review of how you'll use client data — so don't be surprised if you encounter pieces of both depending on which permission or use case triggered the requirement for your app.

Getting This Right the First Time

The businesses that sail through Access Verification are the ones where the paperwork tells one consistent story: the business type they checked, the Platform Data explanation they wrote, and the website they linked all describe the same product in the same terms — and their Business Verification and account standing are already clean before they submit. I handle this end to end for clients — checking prerequisites, writing the Platform Data description, matching it to the website, and submitting — typically within 1–2 days of getting the details from you. If you want a second pair of eyes on your form before you submit it, or want me to run the whole process, that's the kind of work I do through Mojo Web Technology.