Read Visible Post Reactions
View all Facebook Public Data API endpoints →Supply post_id, with optional reaction_type and cursor. The documented reaction choices are like, love, haha, wow, sad and care; select one supported value rather than sending the comma-separated list of choices. This route has not been sampled, so reaction-record fields and filter behavior are unverified. It is separate from the aggregated reaction counts observed in Page-post and search-post responses. Visible reactions are neither complete audience reach nor a built-in sentiment classification.
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/post-reactions API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/facebook-scraper/post-reactions?key=<API_KEY>&post_id=<post_id>'
Query Result
Use Cases
- Evaluate a category-specific reaction sample for a selected campaign post.
- Test individual reaction_type values before defining a reaction-record ingestion schema.
- Compare visible reaction records with aggregate counts without assuming identical coverage.
- Support a privacy-conscious engagement review that avoids profiling individual reactors.
Frequently asked questions
Can reaction_type include all types in one request?
Choose one documented value, such as like or love. Do not send the comma-separated list of choices as a single value.
Should the number of reaction records equal the total post reaction count?
Do not assume equality. The detail endpoint has not been validated, and its coverage may differ from the aggregate count.
Can I treat love or sad directly as a sentiment-analysis result?
No. Reaction categories are not a complete assessment of emotion, nor do they represent audience reach or sensitive personal traits.