Social Fetch
Get API key
All use cases

Facebook group data API

Public group feeds are where local buyers post "ISO" requests, franchise operators compare vendors, and support threads surface product complaints before they hit review sites. Meta does not ship a clean export for any of it. This endpoint gives you paginated posts — text, author handles, timestamps, engagement counts — in the same JSON envelope as TikTok search and Reddit threads.

Try in playgroundView pricing

What usually breaks first

Most facebook groups pipelines fail on schema drift and billing surprises long before they fail on "missing a platform." The notes below are the failure modes we hear about after a DIY scraper or marketplace API is already in production.

Facebook groups are uneven gold mines. A parenting group in Austin surfaces daycare waitlist tips. A contractor trade group names suppliers by city. Buy/sell groups list inventory with prices in the post body. None of that shows up in the Graph API in a form you can poll on a cron job.

Most teams try headless Chrome first. Login walls, infinite scroll, and DOM rewrites break scripts every few weeks. You end up maintaining per-group selectors instead of building the product. Private groups are out of scope for any third-party tool — this page is about public URLs you can pass to an API and get back structured rows.

Social Fetch runs the upstream lookup and returns normalized posts with cursor pagination. You keep the same response shape when Meta rearranges markup. Check data.lookupStatus on every page, bill per completed lookup, and filter keywords in your own pipeline where you already run dedupe and alerting logic.

3 routes for this job

These are the routes we see in live facebook groups integrations — Facebook in this list. Method, path, and query params match the public OpenAPI spec; when we add a field to docs, it ships 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

A common path starts with “map groups to monitoring jobs.” Your cron cadence, warehouse schema, and alert thresholds will differ — treat the steps as ordering hints, not a checklist you must copy verbatim.

  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 key from the dashboard. The playground pre-fills auth if you open the same path there — useful before you paste this into a worker or CI job.

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

You get 100 credits on signup — enough to walk through the curl above against live data and inspect lookupStatus, pagination, and meta.creditsCharged. If the JSON lands cleanly in your pipeline, buy a credit pack once; balances do not expire on a subscription clock.

Open playgroundSee pricing