Search Posts Within a Selected Group
View all Facebook Public Data API endpoints →Supply query and the intended group_id for a group-scoped post search. The schema marks group_id optional, but omitting it does not establish a useful group-specific workflow; provide a confirmed public-group identifier rather than relying on a saved default. cursor, start_date and end_date are optional documented inputs. This route has not been sampled, so matching, field layout and date formats need validation. A query does not enable access to private-group discussions or prove complete topic coverage.
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/search-groups-posts API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/facebook-scraper/search-groups-posts?key=<API_KEY>&query=<query>'
Query Result
Use Cases
- Evaluate product-question discovery within a specifically approved public community.
- Compare a launch-related query across separately confirmed public group IDs.
- Test group_id scoping before enabling a group-specific search feature.
- Validate date-filter behavior in a narrow community sample before scheduling repeated searches.
Frequently asked questions
Can I omit group_id because it is optional for group-scoped search?
To research a specific group, provide its confirmed ID. An optional field does not establish that omitting it leaves a clearly defined group scope.
Can I use a keyword to search private-group content?
No such access is promised. A query term does not change content visibility or access authorization.
Is finding all relevant posts within the group guaranteed?
No. Matching, dates and the response still need validation. Do not treat results as complete topic coverage.