Get a Public Post by URL or ID
View all Facebook Public Data API endpoints →Supply post_id or post_url; when both are supplied, post_id takes precedence. Omit the unused ID when looking up a URL so it cannot override the intended input. This is a documented post-detail route with no sampled response, so no exact envelope or detail fields are asserted. Validate any returned comment and share identifiers before chaining discussion or reshare reads; those identifiers need not equal the visible post ID. Access is limited by public availability, and an unavailable result alone does not prove deletion.
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-post-details API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/facebook-scraper/get-post-details?key=<API_KEY>'
Query Result
Use Cases
- Enrich a submitted public post URL for an editorial fact-checking queue.
- Refresh a saved post reference while retaining the date of each client observation.
- Test URL-only and ID-only request paths without accidental ID precedence.
- Inspect returned identifiers before connecting a selected post to comment or reshare research.
Frequently asked questions
Which input is used when both post_id and post_url are supplied?
post_id takes precedence. To look up a URL, clear the unused ID so that the request does not target a different post.
Has the post-detail response structure been validated?
Not yet. Do not directly reuse the Page-post list fields. Inspect a representative detail response first.
Does failing to retrieve a post mean that it was deleted?
Not necessarily. Visibility or temporary unavailability may also affect the read. Preserve an uncertain state.