What the API does and who it's for
Facebook Scraper, built by DataDwarfs, gives developers programmatic read access to publicly visible Facebook data. The key selling point is straightforward: you do not need a Facebook developer account, user tokens, or a proxy network to make requests. For teams that have been burned by Facebook's own Graph API restrictions — which require app review, user consent flows, and strict data policies — this is a meaningful practical difference.
The typical users are researchers scraping public posts for sentiment analysis, marketers monitoring brand pages and competitor activity, data engineers building social media dashboards, and developers who need structured Facebook data without the overhead of managing OAuth sessions or keeping access tokens fresh.
Endpoint coverage
The API currently lists 43 endpoints. The breadth of coverage is notable — it spans essentially every major content type on the platform:
Search
A dedicated /search/* namespace covers posts (with date filtering), pages, groups, group posts, videos, events, places, locations, hashtags, people, and a global search. The /search/posts and /search/pages endpoints are likely the most frequently used entry points for content discovery workflows.
Pages
The /page/* group includes endpoints for page details, posts (with date filtering), future and past events, photos, videos, reels, and reviews. Being able to paginate a page's post history with date filters makes this useful for longitudinal studies or competitive benchmarking.
Profiles
Profile data is accessible either by URL (/profile/details_url) or by numeric ID (/profile/details_id). There are also endpoints for a profile's posts and photos, plus a utility endpoint to resolve a profile URL to its internal ID.
Posts and comments
You can fetch full post details with /post, retrieve comments with /post/comments, drill into a specific comment with /comment, and enumerate reshares with /post/share. This chain lets you reconstruct a thread without any direct Facebook session.
Groups
Group-oriented endpoints cover details, posts, future events, and ID resolution. This is useful for community research or tracking activity in public interest groups.
Events
Events can be fetched by URL (/event/details) or by ID (/event/details_id). Page-level event listings split into future and past buckets.
Gaming and Marketplace
Less commonly found elsewhere, the /gaming/games and /gaming/live endpoints expose Facebook Gaming content. The /marketplace/search and /marketplace/details endpoints provide access to public Marketplace listings — a niche but genuinely hard-to-scrape surface that could serve price-tracking or inventory tools.
Pricing
The API uses a freemium model with four billing tiers. Overage charges apply on paid plans once the monthly request quota is exhausted.
| Plan | Price/month | Monthly requests | Overage per request | Rate limit |
|---|---|---|---|---|
| BASIC | $0 | 100 | — | — |
| PRO | $4.99 | 1,000 | $0.0100 | 1 req/sec |
| ULTRA | $59 | 30,000 | $0.0050 | 5 req/sec |
| MEGA | $199 | 100,000 | $0.0030 | 20 req/sec |
The BASIC tier's 100 requests per month is only realistic for initial evaluation — it will not sustain any production workload. PRO at $4.99 is a reasonable entry point for light use such as a personal monitoring tool or a low-volume research project; at 1,000 requests and a 1 req/sec rate limit, you could run a modest daily digest without hitting overages. Note that if you exceed 1,000 requests on PRO, each additional call costs $0.01, so an unexpected spike of 500 extra requests adds $5 — doubling the monthly bill.
ULTRA is the recommended tier and offers the best cost-per-request economics before overages: roughly $0.002 per request on the base quota. MEGA at $199 suits higher-volume pipelines, and the overage rate drops to $0.003, making it relatively predictable even if usage fluctuates.
Custom plans are available — the provider accepts requirements via Telegram at @danektech if none of the standard tiers fit.
Practical use cases
- Brand and competitor monitoring: Combine
/search/postswith date filters and/page/poststo track how a brand's public content and mentions evolve over time. - Event intelligence: Use
/search/eventsand/event/detailsto aggregate public event data for local guides or travel applications. - Academic research: Scrape public group posts or hashtag search results for discourse analysis without navigating the official Research API approval process.
- Price comparison / Marketplace tools: The
/marketplace/searchand/marketplace/detailsendpoints are a relatively uncommon offering that could feed a secondhand goods price tracker. - Gaming stream aggregation:
/gaming/livecan surface active game streams, potentially useful for gaming community apps.
Limitations and things to check before integrating
Latency is the most significant caveat. The API's average response time is 3,883 ms — close to four seconds. That is acceptable for background batch jobs and scheduled crawls, but it rules out any user-facing feature where the response needs to appear in real time. The provider acknowledges a known issue where a subset of requests experiences even slower response times and states work is ongoing to address this.
Success rate sits at 96%, meaning roughly 1 in 25 requests fails. Any integration should implement retry logic with exponential backoff. For high-volume pipelines, factor this into capacity planning.
Rate limits are per tier and not stated for BASIC. At MEGA's 20 req/sec ceiling, sustained throughput over a month is still bounded by the 100,000-request quota; at 20 req/sec you could technically exhaust that quota in under 90 minutes, so overage pricing becomes very relevant for burst workloads.
Terms and legality: Scraping Facebook's public data exists in a contested legal and terms-of-service space. Developers should independently review applicable laws (particularly computer access laws in their jurisdiction) and assess the risk profile before building a production system on this API.
Getting started
The API is available through the marketplace and requires no Facebook credentials on your end. Sign up for the BASIC plan to evaluate the response shapes across endpoints before committing to a paid tier. The provider's website is datadwarfs.com, and for custom requirements or individual server arrangements, contact is available via Telegram at @danektech. Given the latency profile, build asynchronous request handling from the start rather than retrofitting it later.
