Social Fetch
Get API key
All use cases

Facebook group data API

Paginated posts from public Facebook groups — text, authors, timestamps, engagement — same JSON envelope as other platforms.

Try in playgroundView pricing

What usually breaks first

Common failure modes after a DIY scraper or marketplace API hits production — schema drift, billing surprises, and pagination quirks.

Public Facebook groups carry local listings, vendor comparisons, and support threads — no Graph API export for polling. Headless Chrome breaks on login walls and DOM rewrites; private groups are out of scope.

GET /v1/facebook/groups/posts returns normalized posts with cursor pagination. Check data.lookupStatus; filter keywords client-side.

3 routes for this job

Routes used in live facebook groups integrations (Facebook). Paths and params match OpenAPI; documented fields ship in responses.

  • GET /v1/facebook/groups/posts

    Core feed for a public group URL. Pass sortBy=chronological for timeline order, chronologicalListings for marketplace-style buy/sell groups, recentActivity when you care about threads with fresh comments, or top for high-engagement posts in the window.

  • GET /v1/facebook/posts/comments

    Comment thread on a group post permalink — useful when the post text is thin but replies carry the signal (pricing negotiations, vendor recommendations, complaint details).

  • GET /v1/facebook/profiles

    Resolve a public page or profile URL when you need to link post authors to a business page, location tag, or cross-platform handle in your graph.

OpenAPI reference →

How teams wire this

Typical order starts with “map groups to monitoring jobs.” Adjust cadence, schema, and thresholds to your stack.

  1. 1

    Map groups to monitoring jobs

    Start with a spreadsheet of public group URLs — city-specific buy/sell, vertical hobby, franchise ops, local services. Tag each row with the sort order it needs: chronologicalListings for marketplace groups, recentActivity when replies matter more than the original post.

  2. 2

    Poll feeds on your cadence

    Hit /v1/facebook/groups/posts per group on a cron or queue worker. Page with data.page.nextCursor until it is null. Each page is a separate billed lookup — budget weekly sweeps differently from hourly buy/sell watches.

  3. 3

    Extract intent from post text

    No server-side keyword filter on this route. Fetch pages, match on body text client-side: "ISO", "recommend", "moving sale", competitor names, SKU fragments. Dedupe by post ID before writing to your warehouse or firing Slack webhooks.

  4. 4

    Pull comments when threads carry the signal

    A one-line "anyone know a good plumber in Round Rock?" post often gets the real answer in replies. Pass the post URL to /v1/facebook/posts/comments and score the thread, not just the headline.

  5. 5

    Enrich for local business intel

    Buy/sell and local service groups encode geography in the group itself — you already know the metro. Join post timestamps with your territory model. Flag listings under market price, recurring vendor mentions, or complaint patterns about a brand you track.

  6. 6

    Scale community management review

    Moderation teams watching dozens of brand-owned or partner groups can pre-filter new posts against policy rules before a human opens Facebook. Route high-risk matches to a review queue; archive everything else for trend reports.

Example: buy/sell group with listing sort

Swap YOUR_API_KEY for a dashboard key. The playground pre-fills auth for the same path.

Request
Example: buy/sell group with listing sort

Why teams skip DIY Facebook scrapers

  • Facebook sits beside Instagram, Threads, Reddit, and web utilities under one API key — cross-platform studies do not need a separate scraper repo per network.
  • Upstream returns a small batch of posts per page with predictable credit cost; no surprise egress bills from a headless browser farm.
  • When Meta changes feed markup, your integration keeps the same field names — you are not rewriting CSS selectors on every deploy.
  • lookupStatus tells you found vs not_found vs lookup_failed before you parse items; infrastructure failures are not charged.
  • Credits do not expire between monthly research windows — poll ten groups weekly or two hundred during a market entry sprint on the same balance.
  • No published rate cap beyond your credit balance; we recommend staying under ~500 concurrent requests so backfills finish without queuing behind your own thundering herd.

Run a facebook groups lookup on free credits

100 credits on signup — run the curl above, inspect lookupStatus and meta.creditsCharged, then buy a pack when ready. Balances do not expire.

Open playgroundSee pricing