Facebook Creator Discovery API permission access is the critical approval step for apps that need real creator discovery data instead of mocked results.
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.
Facebook Creator Discovery API permission: 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.
Facebook Creator Discovery API permission depends on a Business-type app, correct assets, and a clear use case for creator discovery.
Request Facebook Creator Discovery API permission before relying on live creator profiles or engagement numbers.
Document Facebook Creator Discovery API permission requirements in the app review submission and product flow.
Test Facebook Creator Discovery API permission behavior with approved and unapproved app states.
Monitor Facebook Creator Discovery API permission status after deployments and Business Manager changes.
Explain Facebook Creator Discovery API permission limits to stakeholders so mocked data is not mistaken for production access.
Audit Facebook Creator Discovery API permission errors separately from access-token and endpoint errors.
Verify Facebook Creator Discovery API permission guidance in the official Meta Graph API documentation before launch.
Need Us to Get Your Meta App 100% Approved?
Stop losing weeks to repeated rejections. With 500+ apps approved, we handle your entire submission from start to finish. You get 100% Approval or a 100% Refund — and for your complete safety, you can hire us directly through Upwork or Fiverr Escrow (or use the WhatsApp / Calendar buttons in the header & footer).
Chat on WhatsAppFrequently Asked Questions about Creator Discovery API access
Why is Creator Discovery API access refused?
Meta limits this access to clear, legitimate creator-partnership use cases. Requests are refused when the use case looks like bulk profiling or scraping, when the app's data handling isn't explained, or when the business behind the app isn't verified.
How long does it take if you handle it?
It takes ~3 days for our complete preparation and submission, followed by Meta's review queue — typically 10–20 days (can be faster or take longer depending on Meta's volume). For apps with multiple permissions, if Meta requests adjustments on specific scopes, we handle the changes and re-apply at no extra cost, and each follow-up round follows the same 10–20 day review window.
What if it still isn't approved?
We work on a 100% Approval or 100% Refund basis: if we can't get your valid use case approved, you get a full refund.
Is it safe to hire you?
Yes. You can hire us through Upwork or Fiverr, so your payment stays in Escrow and is only released when the work is delivered. We've been doing this for 10+ years, with 500+ apps approved and 10,000+ permissions granted.