Facebook Marketplace Scraper — No Login | GPS, Photos

Facebook Marketplace Scraper — Listings, Prices | from $2/1K

Scrape Facebook Marketplace listings by location, keyword, category, and price range.

Returns title, price, condition, description, city/state, GPS coordinates, image URLs, listing URL, and posted time — no Facebook login required for public listings.

What you get per listing

Field	Source	Notes
id	Search	FB listing ID
title	Search	Listing title
price	Search	Formatted string, e.g. "$450"
price_amount	Search	Numeric (450.0)
currency	Search	Usually "USD"
condition	Detail	New / Used - Good / Used - Like New / etc.
description	Detail	Full listing description text
city / state	Search	Approximate location
location	Search	Display string, e.g. "San Francisco, California"
latitude / longitude	Detail	Precise GPS coordinates
image_urls	Detail	All image URLs
thumbnail_url	Search	Primary thumbnail
image_count	Detail	Count of images
listing_url	Computed	facebook.com/marketplace/item/<id>/
posted_time	Detail	ISO 8601 timestamp
delivery_types	Search	IN_PERSON, DOOR_PICKUP, SHIPPING
is_sold	Detail	Boolean
seller_name	—	Not available — Facebook hides this for logged-out users
parse_confidence	QA	0–1 quality score

Known limitation

Seller name is not returned for anonymous (logged-out) access. Facebook hides it for privacy — seller_name will always be null. This is a platform-level restriction, not a parser limitation. Workaround: login-based scraping (requires credentials; not supported by this actor).

Inputs

Input	Required	Default	Description
location	✓	newyork	City slug from Marketplace URL (e.g. sanfrancisco, losangeles, chicago)
query		—	Search keyword (e.g. iphone 14, sofa)
categoryId		—	FB virtual category ID
priceMin / priceMax		—	Price filter in USD
radiusKm		65	Search radius in km
maxItems		50	Max listings to return
enrichDetails		true	Fetch full detail per listing (description, all images, condition, GPS)
proxyConfiguration		RESIDENTIAL	Apify Residential proxy recommended

Access method

Uses Facebook's internal GraphQL API (/api/graphql/) — the same endpoint the Marketplace web app calls. No HTML scraping, no browser. The LSD token and live doc_ids are re-extracted from the page on every run, making the actor resilient to FB deploy rotations.

Access notes

• Facebook checks IP reputation. Datacenter IPs return empty results or login walls — always use RESIDENTIAL proxy on cloud.
• Cursor pagination is disabled for anonymous sessions; price-range slicing is used to return >24 listings per query.

💰 Pricing & how we compare

Pay-per-result (PPE): from $1.49 / 1K listings. You are billed per listing-item actually returned — plus the tiny apify-actor-start fee Apify waives for short runs. No subscription, no API key, no proxy fee on top.

Our edge: No login or cookies · keyword + location + radius search · per-listing detail enrichment (all photos, condition, seller, GPS) · parse_confidence on every row.

Pricing examples (pay only for what you get, minus Apify's 20%):

Volume	Cost
100 listings	$0.15
1,000 listings	$1.49
10,000 listings	$14.90

How rivals price the same job (live Apify Store, checked 2026-06-09)

Actor	Their price	What they lack vs us
apify/facebook-marketplace-scraper	$6.20/1K	king (3.3★) but needs start URLs — no keyword/location search
crowdpull/facebook-marketplace-scraper	$5.00/1K	no-login peer, but no per-listing detail depth
memo23/facebook-marketplace-scraper-ppe	$1.50/1K	5★, but thinner per-listing fields

Prices above are competitors' live Store prices at the time of writing; ours is set to sit just below the strongest comparable while returning richer, quality-scored data.

🤖 Use with AI agents (MCP)

This actor is agent-ready (category MCP_SERVERS). Point any MCP client (Claude Desktop, Cursor, n8n AI, LangGraph) at it:

{
  "mcpServers": {
    "apify": {
      "url": "https://mcp.apify.com/?actors=bovi/facebook-marketplace-scraper",
      "headers": { "Authorization": "Bearer <YOUR_APIFY_TOKEN>" }
    }
  }
}

More scrapers from our toolkit

Building a data pipeline? These actors pair well with this one — each runs on your own Apify account with the same pay-per-result pricing, no subscription:

• Grailed Listings
• Kleinanzeigen Listings Scraper
• Leboncoin Listings
• Marktplaats Listings Scraper
• Mercadolibre Scraper
• Olx Listings

Chain any of them together from the Integrations tab (the Run succeeded trigger) to build a multi-step workflow — one actor's output feeds the next.

Usage statistics

This Actor creates a small, content-free summary at the end of each run. It is used only to monitor reliability and improve this Actor. A copy is saved as USAGE_STATS in your own Apify key-value store, so you can see the exact record created for your run.

Set disableUsageStats to true in the input to opt out. Nothing is sent then; your USAGE_STATS record only says that statistics were disabled.

Only these fields are recorded:

• schema version, Actor name and build number;
• UTC start and finish hour (not a precise timestamp);
• run duration, number of results and time to the first result, each as a coarse range;
• whether the result was empty, the end status, and an error type from a fixed list;
• memory setting and counts of charged events;
• names of the input fields you set, never their values;
• the selected option for input fields that offer a fixed list of choices (for example a sort order).

We do not collect input text, search terms, URLs, domains, usernames, email addresses, names, proxy credentials, tokens, scraped records, output items, raw error messages, stack traces, or hashes of any of those values. Records are kept for no longer than 13 months, used only as aggregated operational statistics, and never sold or shared.

Additional fields (Phase 2)

This Actor also records your Apify user ID, whether Apify marks the account as paying, the size range of list inputs, the selected country when the input offers a fixed list of countries, and one category from a fixed Actor taxonomy. We use these fields only for aggregate reliability, repeat-use and cross-Actor analysis; reports suppress any cell with fewer than five distinct users.

The same disableUsageStats: true input flag turns these fields off too. The user ID is removed after 13 months; we do not export, sell, share, or attempt to re-identify this data.

Run-outcome signals (v2)

To learn whether a run did what it was asked to do, the record also holds a few more coarse ranges and yes/no flags. None of them contains content:

• the result limit you asked for (a range, when the input has one) and what share of it was delivered;
• results delivered per input item you listed (a range);
• output quality as ranges: how fully the result fields were filled, the share of rows that look like errors, the share of duplicate rows, and how many different fields appeared. These are counted in memory while results are saved; no result content is kept;
• how the run was started (console, API, schedule, webhook, another Actor);
• how it ended: stopped by you, timed out, reached the requested limit, stopped by the charge limit, and how many times the platform moved the run;
• if this Actor reports it: how many items to process worked or failed (ranges) and one failure reason from a fixed list;
• a short code made from the names of the input fields you set, never their values.

Repeat-run fingerprint (v2)

When your Apify user ID is recorded (see above), the record also holds an 8-character one-way code made from your input (proxy settings left out) and this Actor's name. It only lets us see that the same account ran the same input again soon after an unsatisfying run; we never see the input itself. It is stored only in the database, never published, and reports use it in aggregate with the same five-user minimum. It is the one exception to the statement above that no hashes are collected, and disableUsageStats: true turns it off.