Resolve a Group ID from a URL
View all Facebook Public Data API endpoints →Supply a group url to request its documented Facebook identifier. No response for this resolver was sampled; verify the returned field and identifier before passing it as group_id to content routes. A resolved ID normalizes a reference but does not prove that the group is public or that its content is available. Preserve the original URL when reconciling group references and avoid treating identity resolution as access authorization.
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/get-group-id API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/facebook-scraper/get-group-id?key=<API_KEY>&url=<url>'
Query Result
Use Cases
- Normalize alternate community links before scheduling any permitted group-content read.
- Deduplicate a reviewed source list using confirmed group identifiers.
- Validate URL-to-group_id handoff in a small integration test.
- Require a separate public-access check after resolving a submitted group reference.
Frequently asked questions
Does obtaining group_id prove that a group is public?
No. Identifier resolution does not establish content visibility. Public-access conditions need separate validation.
Can I pass the resolver result to content endpoints without checking it?
This is not recommended. There is no representative sample of the returned fields. Verify that the identifier actually belongs to the intended group.
What should I retain when merging group URLs?
Save both the confirmed group_id and the originally submitted URL to check the source and avoid incorrect merges.