Facebook Public Profile Posts API - Creator Content Reads

Supply profile_id and optionally cursor, start_date or end_date. This documented route requests recent posts when public, but it has not been sampled; neither the Page-post envelope nor its detailed fields are guaranteed here. Date input formats and behavior also need validation. Use only public-figure content or an appropriate, permission-aware creator workflow, and stop bounded traversal on an absent or repeated continuation value. Historical completeness and non-public posts are not promised.

API Features

Public-profile timeline scope Targets visible profile posts rather than a business Page timeline.

Profile-specific post cursor Keep continuation values tied to the selected profile-content request.

Unvalidated date-bound inputs start_date and end_date are exposed without inventing an accepted date format.

Limited historical expectations Public visibility and pagination do not establish access to every past post.

Live API Demo

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

API Response (JSON)

{}

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

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

📢

Need Help?

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

Use Cases

Evaluate an opted-in creator public-post history for campaign-content review.
Build a deduplicated client-side record of a public figure's visible posts after checking the actual fields.
Test profile date-bound behavior independently of Page-post filtering.
Compare observed creator posting themes without attributing private or unavailable content.

Frequently asked questions

Can I reuse a Page-post parser for profile posts?

Do not assume so. This endpoint has no independent sample. Validate the actual envelope, identifiers, text and other fields.

Can date filters guarantee coverage of the entire historical range?

No. Date formats and behavior still need validation, and historical coverage is also limited by public visibility.

How can I bound continuation through profile posts?

Set a page or request limit, stop on an empty or repeated cursor and deduplicate using validated post identifiers.

Related operations

Guides

View Subscription Plans →

Read Public Profile Posts