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

Known-profile-key lookup Starts from a stored profile_id instead of requiring a profile URL.
Independent ID-route contract The sampled URL-route schema is not automatically attributed to this untested endpoint.
Authorized record reconciliation A confirmed public profile key can support joins across client observations.
Profile data minimization Retain only the public attributes appropriate for the permitted research or creator workflow.

Live API Demo

GET /api/project/facebook-scraper/profiles-details-by-id

Request cost is temporarily unavailable. No price is assumed.

View pricing

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>'
📢
Need Help?
If you encounter API issues or need other API requirements, please contact us.
Contact Us

Use Cases

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.

Related operations

Guides

View Subscription Plans →