Resolve a Public Profile ID from a URL
View all Facebook Public Data API endpoints →Provide a public Facebook profile url to request its identifier. The resolver is documented but was not sampled, so no exact return key or envelope is guaranteed. Validate the identifier before using ID-based profile or content routes. The sampled profile-details-by-url route is an alternative when you also need the visible name and profile context. URL normalization should preserve the original submitted link for human identity checks; it does not establish consent or access to non-public content.
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/profile-id API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/facebook-scraper/profile-id?key=<API_KEY>&url=<url>'
Query Result
Use Cases
- Normalize consenting creator profile links before storing ID-based references.
- Reconcile alternate profile URLs without discarding the original submission.
- Separate person-profile submissions from organization-Page submissions in an intake form.
- Validate profile-resolver output before enabling a subsequent creator-content request.
Frequently asked questions
Can I read private posts after resolving a profile ID?
No. Resolving an identifier does not change visibility or replace consent or appropriate authorization.
Which endpoint should I use if I also want a name?
Consider the URL-based public-profile lookup, which has a validated sample with a visible name and profile context.
Should I retain the original URL after normalization?
Keeping it is recommended for human confirmation of the resolved subject and tracing the submission source, avoiding incorrect merges of people with the same name.