Facebook Public Group Posts API - Chronological or Top Posts

Provide group_id, optionally cursor and one sorting_order value: CHRONOLOGICAL or TOP_POSTS. Documentation limits this route to public groups; an empty or unavailable response warrants checking public visibility rather than assuming no discussions exist. No group-post response was sampled, so post fields, ordering behavior and result envelope remain unverified. Use bounded sampling, maintain observation times and validate IDs before deduplication. The sorting controls do not promise a complete historical archive.

API Features

Public-community content scope The documented read applies to public groups rather than hidden community discussions.

Two group-post ordering choices Select CHRONOLOGICAL or TOP_POSTS as one sorting_order value.

Group timeline continuation A cursor can continue the same group-post request with its selected ordering.

Empty-output accessibility check Unreadable or empty content must not automatically be interpreted as an inactive community.

Live API Demo

GET /api/project/facebook-scraper/get-group-posts

API Response (JSON)

{}

curl -X GET 'https://api.opendata-api.com/api/project/facebook-scraper/get-group-posts?key=<API_KEY>&group_id=<group_id>&sorting_order=CHRONOLOGICAL'

curl -X GET 'https://api.opendata-api.com/api/project/facebook-scraper/get-group-posts?key=<API_KEY>&group_id=<group_id>&sorting_order=CHRONOLOGICAL'

📢

Need Help?

If you encounter API issues or need other API requirements, please contact us.

Use Cases

Evaluate bounded public-group discussion samples for recurring product questions.
Compare chronological and top-post samples after testing the actual ordering.
Store validated group post IDs to avoid re-analyzing duplicate client observations.
Review public visibility before interpreting a group-content request as a no-discussion result.

Frequently asked questions

Which value should I use for sorting_order?

Choose one of CHRONOLOGICAL or TOP_POSTS for each request. The exact ordering behavior still needs validation against responses.

Do empty group-post results mean that the group is inactive?

Do not infer that. Check public group visibility and current availability first, then assess the business status.

Can chronological continuation retrieve the entire group history?

This is not guaranteed. Limit requests, record collection times and deduplicate using validated post identifiers.

Related operations

Guides

View Subscription Plans →

Read Public Group Posts