Facebook reference
Facebook API guide
Read a public page, choose a post from its feed and inspect the available discussion. Pages, groups, reels and marketplace listings are separate data surfaces.
Quickstart
Start with Facebook
Read a public page, choose a post from its feed and inspect the available discussion. Pages, groups, reels and marketplace listings are separate data surfaces.
These requests use your API key and can spend credits. Check the current price on the endpoint page; each new page is a separate request. Later examples use illustrative identifiers: replace them with values from your earlier response.
1. Resolve the page
Keep the returned page URL and source identifiers. Page followers and likes describe different counters. Parameters and current cost →
curl "https://www.monocrawl.com/v1/facebook/profile?url=https%3A%2F%2Fwww.facebook.com%2Fnasa" \ -H "x-api-key: mn_your_key_here"
2. Read the page feed
Choose a returned post URL. A page of posts is a bounded sample, and feed order may include pinned content. Parameters and current cost →
curl "https://www.monocrawl.com/v1/facebook/posts?url=https%3A%2F%2Fwww.facebook.com%2Fnasa" \ -H "x-api-key: mn_your_key_here"
3. Read a post discussion
Replace the example URL with a post from the feed. Preserve reply continuation fields on each comment. Parameters and current cost →
curl "https://www.monocrawl.com/v1/facebook/post-comments?url=https%3A%2F%2Fwww.facebook.com%2Freel%2F2839681326387786%2F" \ -H "x-api-key: mn_your_key_here"
Filters and coverage
Choose filters with the source behavior in mind
| Control | Behavior and limits |
|---|---|
| URL identity | Use the correct public page, post or group URL. A page name does not resolve to a group and a numeric counter is not a list of people. Endpoint reference → |
| Reply continuation | Pass feedback_id and expansion_token from the same parent comment together. Neither can be reconstructed from the display text. Endpoint reference → |
| Sort and time | Group sort_by supports CHRONOLOGICAL or TOP_POSTS. City event time buckets belong to city-events; do not attach them to other feeds. Endpoint reference → |
| Coverage | A visible comment count does not guarantee every comment or reply can be collected. Preserve the returned cursor and warnings. Endpoint reference → |
Source availability, ordering and field coverage can change. Inspect warnings and partial-result metadata alongside the rows. See runnable workflows, metric semantics, computed fields and the pagination matrix.
Choose an endpoint
Match the operation to your task
| Your task | Endpoint | When to use it |
|---|---|---|
| A specific post | post | Retrieve its full available text and counters. |
| Replies under a comment | comment-replies | Requires both feedback_id and expansion_token from that comment row. |
| A public group feed | group-posts | Use a group URL and its supported sort. A page feed does not retrieve group posts. |
| Events around a city | city-events | Use a city events URL and the declared time bucket. |
Explore all documented operations by purpose below. Each endpoint reference contains its accepted parameters and current price.
Comments and replies
Search and discovery
Posts and media
Transcripts
Accounts and audiences
Operations
Each row is a registry operation: expand it for parameters, a curl built from the registry's own examples, and a Markdown copy of the whole entry. The badge on the right is the operation's state, read at request time — we publish all three rather than rounding up. Recorded proof is historical, not a guarantee of current availability.
- live · proven
- a real upstream response has been served through this API and recorded
- wired · unproven
- a real-data route is registered, but qualifying proof is absent; permission or capacity restrictions may apply
- sample · free
- no live upstream — /v1 refuses it, /sandbox returns a marked sample
Catalogue only
Designed, not yet wired
These ids are in the Facebook catalogue but have no registry row, so they are targets rather than operations. On /v1 each answers 501 ENDPOINT_NOT_AVAILABLE at no charge; the same path under /sandbox returns a representative sample marked synthetic: true. They are listed separately so you can distinguish planned coverage from the operations available above.
/v1/facebook/page/v1/facebook/page-reviews
Elsewhere
The same registry, other shapes
- Facebook overview — supported data categories and use cases for this platform.
- Full endpoint reference — every platform on one page.
/openapi.jsonor/openapi.yaml— the machine-readable contract, for Postman, Insomnia or a client generator.GET /v1/utility/endpoints?platform=facebook— the same rows to your code at runtime, for 0 credits.