What the API does and who it is for
Facebook Pages Scraper is a hosted scraping suite that turns public Facebook data into clean, machine-readable JSON. Rather than fighting Facebook's unofficial endpoints or managing browser automation yourself, you send a standard HTTP GET request and receive structured fields back. The API covers six distinct data domains: Facebook pages, groups, posts, search results, marketplace listings, and Meta Ads Library records.
The typical integrators are agencies running competitive analysis on brand pages, researchers tracking group engagement, e-commerce teams monitoring Marketplace pricing, and marketers auditing ad campaigns through the Ads Library. It is not an official Facebook API, so the usual caveats around scraping apply — data availability depends on what Facebook exposes publicly, and session cookies for private pages have an expiration lifecycle that the API signals via HTTP 203.
Endpoint walkthrough
With 36 endpoints spread across six functional groups, there is a lot of surface area. Here is what each group actually delivers:
Facebook pages (7 endpoints)
The core offering. GET /get_facebook_pages_details accepts one or more page URLs and returns a rich object: title, bio, about text, category, creation date, follower and like counts, email, phone, address with a Google Maps link, business hours, price range, services, rating, profile image URL, ad status, and the page's ad ID. The sample output shows all of this in a single response per URL.
GET /get_facebook_posts_details retrieves up to three posts per call, with cursor-based pagination for deeper fetches. Companion endpoints cover reels (up to 10), videos (up to 6), albums (up to 8), and album media items. A utility endpoint (/get_facebook_page_id) resolves a page URL to its internal numeric ID, which other endpoints may require.
Facebook groups (6 endpoints)
Mirrors the pages group in structure. Group details include member count, new member count, creation date, and activity summaries. Posts, videos, albums, and album media endpoints follow the same pagination pattern.
Facebook posts (7 endpoints)
The most granular data domain. /get_facebook_post_details accepts a post URL or post ID. /get_facebook_post_comments_details returns up to 10 comments per request with cursor pagination and an include_reply_info flag that, when set, provides the comment_feedback_id and expansion_token values you need to call /get_facebook_post_comment_replies. Attachment and reaction data (likes, loves, shares, etc.) come from /get_facebook_post_attachement_details. Video posts have a dedicated endpoint that exposes title, description, duration, and view count.
Facebook search (6 endpoints)
Search across people, pages, posts, videos, and locations by query string and optional location_uid. A city_id-based endpoint (/fech_search_top_places) retrieves top places for a given city. All search endpoints support cursor pagination.
Meta Ads Library (5 endpoints)
This group is useful for ad intelligence work. You can search ads by keyword with filters for country, status (active/inactive), and ad type. A separate endpoint retrieves up to 26 ads per request by page query. Archive ad detail lookup requires an archive_id and supports filtering by page ID, country, and political/non-political flags. A utility endpoint lists supported country codes to avoid filter errors.
Facebook Marketplace (5 endpoints)
Marketplace search accepts a keyword plus filters for location, price range, date range, radius, category, and sort order. Individual listing detail retrieves price, status, primary photo, seller info, delivery options, and comparable listings. A city coordinates endpoint turns a city name into lat/long values for use as location filters, and a categories endpoint provides the seo_url and category ID needed for category-filtered searches.
Pricing breakdown
| Plan | Monthly price | Requests included | Rate limit | Overage per request |
|---|---|---|---|---|
| BASIC | $0 | 25 | — | — |
| PRO | $49 | 3,000 | 1 / second | $0.0100 |
| ULTRA (recommended) | $99 | 10,000 | 3 / second | $0.0070 |
| MEGA | $300 | 50,000 | 5 / second | $0.0040 |
The BASIC tier's 25 monthly requests is effectively an evaluation quota — enough to validate the response schema and test a handful of pages, but not enough for any recurring workflow. At PRO, the math on overage matters: at $0.01 per request you would spend another $70 to exhaust the equivalent of the next tier, so ULTRA becomes cost-efficient once you regularly exceed 3,000 requests. MEGA's $0.004 overage rate is the most economical for high-volume pipelines.
Because each page detail, post, or marketplace item is a separate request, estimate your monthly quota carefully. A workflow that monitors 50 Facebook pages daily (page details + latest posts) could burn through 3,000 requests in under two weeks at PRO.
Practical use cases
Lead generation and contact enrichment: Feeding a list of competitor or prospect page URLs through /get_facebook_pages_details yields phone numbers, emails, addresses, and websites in a single pass — data that would otherwise require manual copy-paste.
Marketplace price monitoring: Retailers and resellers can poll /get_facebook_marketplace_items_listing on a schedule to track price movements for specific product categories across geographic areas.
Ad intelligence: Marketing teams can pull active ads for a competitor's page through the Ads Library endpoints and track creative changes over time without needing access to Meta's own Ads Manager.
Social listening: The group and post endpoints allow researchers to track engagement trends — reaction counts, comment volumes, and post frequency — without requiring Facebook login in the client application.
Limitations and things to check before integrating
Latency: The 7,193 ms average response time is the most significant engineering constraint. This API should not sit in a synchronous user-facing request path. Build around it asynchronously — queue jobs and store results rather than waiting inline.
Request-based quotas: Every endpoint call counts against your monthly limit regardless of how much data it returns. Endpoints that paginate (posts return 3 per call, videos 6, etc.) mean that retrieving deep history is quota-intensive.
Private page handling: HTTP 203 signals that a private page was encountered and session cookies may have expired. If your target pages have any restricted visibility, plan for this response code and build retry or alerting logic around it.
HTTP 202 and 206: The API uses HTTP 202 to flag input validation failures and HTTP 206 for partial results. Standard HTTP clients treat both as success, so you must inspect status codes explicitly rather than relying on a non-2xx exception.
Terms of service: Scraping Facebook is subject to Facebook's own platform policies. Evaluate your use case against those terms, particularly for commercial applications.
Getting started
The API lives on RapidAPI at the URL provided by the publisher. Authentication follows RapidAPI's standard header-based key mechanism. The simplest first call is GET /get_facebook_pages_details with a link query parameter pointing to any public page URL. The response schema shown in the sample output above is what you can expect back. Use /get_facebook_page_id first if downstream endpoints require the numeric page ID rather than the slug URL. For paginated endpoints, capture the end_cursor value from each response and pass it as a parameter in the next call to walk through additional records.
