Facebook Creator Discovery API: Why facebook_creator_marketplace_discovery Sits Behind Advanced Access
Meta's Facebook Creator Discovery API gives brands authenticated, real-time first-party data to find creators for partnership ads. But the permission that powers it, facebook_creator_marketplace_discovery, is locked behind Advanced Access, and most apps only discover this after the integration is already built.
What Meta Requires
- App must be registered as a
Businesstype app, not a Consumer app - Two permissions together:
facebook_creator_marketplace_discoveryandpages_show_list - Brand admin logs in via Facebook Login and accepts the Creator Discovery Terms of Service before onboarding completes
- Requests run on a Page access token, not a user token
Where Apps Get Stuck
- Standard Access only returns simulated (mocked) creator data, never real profiles or engagement numbers
- Both permissions need Advanced Access approval before any brand outside your own app roles can use it
- App Review requires implementation evidence showing the exact discovery and content-search flow in use
- Rate limits apply per account (2,000 requests/hour) and per app (10,000 requests/hour) on top of the review requirement
The Mocked-Data Trap
- Every new app defaults to Standard Access, which silently swaps in simulated creator profiles, so the integration appears to work in testing and then returns nothing usable in production
- Creators only appear in search results if they have opted in to data sharing, so even after Advanced Access is live, discovery results depend on program participation, not just your query
- Branded content fields are restricted to the sponsoring brand's own access token, so a generic Page token will not surface partnership data for other brands
Business-type app and permission pairing
Confirm the app category and request both required permissions together. Submitting them separately is a common cause of review delay.
Standard Access test flow
Build and demonstrate the discovery and content-search calls against mocked data first, since that is what reviewers expect to see reproduced in the screencast.
App Review submission
Provide the use-case narrative, screencast, and Page access token flow that matches how brand admins will actually use the feature.
Advanced Access and real data
Once approved, brand admins re-authenticate, accept the Creator Discovery Terms of Service, and the API starts returning live creator and content insights instead of simulated values.
Most rejections on this permission trace back to two things: requesting facebook_creator_marketplace_discovery without pages_show_list in the same review, or submitting evidence that shows the mocked-data flow instead of the real discovery and content-search use case Meta expects to see.
Getting the Business-type app setup, the permission pairing, and the review evidence right the first time is exactly the kind of submission work I handle for clients. See my Facebook App Review service or hire me as a Facebook API developer if your Creator Discovery integration needs this taken off your plate.