Facebook Page Posts API - Text, Media & Cursor Pagination

Supply page_id from page-details and omit cursor for the first request. The observed body contains results and a cursor string. Posts include post_id, url, message, message_rich, numeric timestamp, author, authors, comments_count, reactions_count, reshare_count, reaction-category counts and nullable media fields such as image, video and video_files. comments_id and shares_id were also present; preserve these endpoint-specific identifiers rather than assuming every downstream route uses post_id. Treat top_comments as a preview, not the whole discussion. Follow returned cursors unchanged with a request bound and ID deduplication; complete history is not guaranteed. start_date and end_date are documented inputs, but their exact formats and behavior have not been validated.

API Features

Post records with UTC conversion Observed numeric Unix timestamps can be converted to UTC alongside message text and post URLs.

Reaction and discussion counts The sample includes total reactions, per-category reactions, comments_count and reshare_count.

Mixed-format Page content Nullable image, video and video_files fields distinguish content formats without promising every media type on each post.

Bounded Page timeline traversal Carry the returned cursor forward and deduplicate post_id values in your application.

Live API Demo

GET /api/project/facebook-scraper/pages-posts

API Response (JSON)

{}

curl -X GET 'https://api.opendata-api.com/api/project/facebook-scraper/pages-posts?key=<API_KEY>&page_id=100064860875397'

curl -X GET 'https://api.opendata-api.com/api/project/facebook-scraper/pages-posts?key=<API_KEY>&page_id=100064860875397'

📢

Need Help?

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

Use Cases

Implement a Python Page-post collector that stops on null or repeated cursors and caps request count.
Compare observed publishing cadence across selected competitor Pages using UTC timestamps.
Annotate text, image and video formats in a rights-aware brand-content audit.
Keep time-stamped engagement observations per post to compare later client-collected snapshots.

Frequently asked questions

How do I fetch the next page of Page posts in Python?

For the first request, pass only the confirmed page_id. Read the returned cursor and pass it unchanged to the same endpoint. Set a page limit and check for repeated cursors and post_id values.

Does having a cursor let me retrieve all historical posts?

This is not guaranteed. Public availability and historical coverage can change; pagination only indicates that continuation context is currently available.

What format should I use for the date parameters?

start_date and end_date are documented, but their formats and effects have not been validated. Test on a small scope first rather than assuming a date syntax.

Related operations

Guides

View Subscription Plans →

Read Recent Page Posts