Get Public Profile Details by ID
View all Facebook Public Data API endpoints →Supply a known profile_id to request public profile details without resolving a URL first. This route has not been sampled; the separately observed URL-based profile response must not be assumed to define its exact envelope or fields. Validate representative output and minimize any personal data retained. A stable identifier helps join authorized observations but is not an identity-verification certificate, and it does not grant access to private profile information.
API Features
Live API Demo
🔒 Sign in to try it live
Log in to call this API with your own API key. New accounts get 100 free credits — no card required.
Log in / Sign upNo active API key found. Create one in your Dashboard, then reload this page. Dashboard →
/api/project/facebook-scraper/profiles-details-by-id API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/facebook-scraper/profiles-details-by-id?key=<API_KEY>&profile_id=<profile_id>'
Query Result
Use Cases
- Refresh an opted-in creator directory keyed by confirmed profile IDs.
- Reconcile authorized public-profile observations from separate research jobs.
- Compare ID-based and URL-based profile outputs during a representative response test.
- Review an ambiguous stored creator identifier before joining personal attributes from another dataset.
Frequently asked questions
Can I use a Page ID instead of profile_id?
Do not interchange them. This endpoint targets profiles, so use a profile_id confirmed to belong to the intended public profile.
Do ID-based and URL-based lookups return the same fields?
This is not yet known. This route has not been independently validated; validate its envelope and fields separately.
Does a stable ID amount to real-world identity verification?
No. It helps link authorized records but does not prove real-world identity or extend access to private information.