We need your help to keep this website free. You can 
Meta is removing a separate Access Verification review for developers whose apps use business data belonging to clients. The change simplifies one part of onboarding. It does not turn Facebook or Instagram data into an unrestricted resource, and it does not replace the permission checks required for an app to do its job.
Source: Meta for Developers, official announcement artwork, cropped and resized. This is Meta's illustration, not an app approval screen or our independent test.
Which review is disappearing?
Access Verification was introduced in 2022 to assess whether a business seeking another business's data was genuinely operating as a Tech Provider. The change was reported on Sunday, following Meta's developer announcement late last week. The company says its other review systems now cover the signals that this separate step was meant to examine.
The practical change is in the onboarding path: the submission form and status field are being removed from App Dashboard. API endpoints will no longer reject a call solely because that separate review has not passed. Here, an API is the interface through which software makes a request; removing one gate is not the same as granting every possible request.
Does an app still need approval?
Yes, where the remaining requirements apply. Meta's published scope keeps Business Verification for access to other businesses' data and App Review for advanced permissions. Data-handling policies and assessment obligations remain. Developers should separate the questions “Is this business verified?” and “May this app use this permission?” rather than treating them as one badge.
App classification also needs attention. Adding an app to a business will no longer automatically alter its business use. Direct Integrator becomes the default; Tech Provider classification follows an explicit upgrade or the advanced permissions requested by the app.
For a creator, check the service rather than the headline
Someone using a third-party publishing service can ask which permissions it requests and what data it stores. A Meta-built feature, such as the assistant inside Edits, is a different workflow from connecting an outside developer's app. This update should not be read as a promise of new functionality in either one.
Campaign-specific rules are separate again. Teams affected by Meta's political-ad delivery cutoff still need to check that policy on its own terms. A shorter developer review path is useful; it is not a general exemption from data or advertising rules.
