Facebook Marketplace Scraper

Extract public Facebook Marketplace listing IDs, URLs, titles, displayed prices, locations and a primary image from search, city, category or individual listing URLs. Use the dataset for local inventory research and price comparisons, then export it to CSV, JSON or Excel.

Facebook must expose the listing without a login. Seller details, full descriptions and availability flags are not extracted. Results are a sample of visible listings, not a complete inventory.

Quick start

1. Copy a public Facebook Marketplace URL for your city and search.
2. Paste it into Facebook Marketplace URLs and choose a small listing limit.
3. Start the Actor and open its dataset to inspect or download the results.

{
  "startUrls": [{ "url": "https://www.facebook.com/marketplace/nyc/search/?query=desk" }],
  "maxItems": 5
}

Prefer a video guide? This short Apify walkthrough shows you how to set up and run an Actor. It uses a different Actor, but the setup steps are the same.

Ready-to-run examples

Choose a public example to see its settings before starting a run:

• Export Facebook Marketplace listings via API input
• Export Facebook Marketplace furniture listings
• Export Facebook Marketplace car listings

What you get

One row per saved visible listing, with its identifier, source link and available title, displayed price, location and primary image. The image array contains at most that same single image. Seller details, descriptions and availability flags remain unpopulated as documented below.

Who is it for?

• Resellers and buyers: Compare asking prices for locally listed items.
• Market researchers: Collect bounded samples from city or category searches.
• Automation teams: Feed listing rows into spreadsheets or your own comparison workflows.

How you can use the data

• Prepare a New York desk-price sample. Use the existing NYC desk-search URL with a small total cap. Keep id, listingUrl, priceText, locationText and scrapedAt together. These are visible asking-price observations rather than completed-sale prices.
• Review a furniture or car category sample. Use the existing public examples or your focused city/category URL. Inspect returned titles and source links before treating the bounded sample as relevant, without assuming complete local inventory.
• Inspect one known listing's visible record. Supply its public listing URL and a one-item cap. Optional prices or images can be missing, and direct-listing input does not enable seller details or description enrichment.
• Compare your own dated exports. Match listing IDs in separate datasets to inspect visible price or title changes. Keep the original price text: a dollar symbol is labeled USD by a parsing heuristic rather than independently verified currency. Cross-run comparisons and alerts belong in your own workflow.

Input settings

Setting	JSON key	Meaning
Facebook Marketplace URLs	startUrls	Required public search, city, category or individual listing URLs.
Maximum listings	maxItems	Total saved-row limit across all URLs. 1–10,000. The form starts with 5 and the schema default is 20.
Proxy configuration	proxyConfiguration	Existing Apify Proxy or custom-proxy settings. See field help for route-specific behavior and defaults.

Use a focused query and location in the URL. There is no separate keyword, radius, sorting or detail-extraction option. Listings are returned in discovery order, with duplicate IDs removed within the run. maxItems is a ceiling, not a guarantee.

Example inputs

Use the Quick start input as a small first run. Adjust the fields described above for your own data.

Output data

Each listing becomes one dataset row. This is an illustrative shape-only example, not a recorded listing:

{
  "id": "1234567890",
  "listingUrl": "https://www.facebook.com/marketplace/item/1234567890/",
  "sourceUrl": "https://www.facebook.com/marketplace/nyc/search/?query=desk",
  "title": "Example desk",
  "priceText": "$80",
  "priceAmount": 80,
  "currency": "USD",
  "locationText": "New York, NY",
  "city": "New York",
  "state": "NY",
  "primaryImageUrl": null,
  "imageUrls": [],
  "deliveryTypes": [],
  "isLive": null,
  "isPending": null,
  "isSold": null,
  "sellerName": null,
  "sellerId": null,
  "description": null,
  "attributes": {},
  "createdAt": null,
  "detailStatus": "not_requested",
  "scrapedAt": "2026-10-24T12:00:00.000Z"
}

Fields	Returned information
id, listingUrl, sourceUrl	Listing identifier, canonical URL and input URL.
title	Visible listing title.
priceText, priceAmount, currency	Displayed price and parsed amount when recognized. Currency parsing recognizes dollar, euro and pound symbols. A dollar symbol is labeled USD, not independently verified currency.
locationText, city, state	Location text and parsed city/state when recognized.
primaryImageUrl, imageUrls	At most one discovered image. imageUrls contains that same image, not a full gallery.
scrapedAt	Time the row was prepared.
deliveryTypes, attributes	Reserved fields, currently always an empty array and object.
isLive, isPending, isSold, sellerName, sellerId, description, createdAt	Reserved fields, currently always null.
detailStatus	not_requested for search/city/category results. not_available for individual listing URLs. There is no detail-enrichment switch.

A RUN-SUMMARY record in the run's key-value store describes saved, skipped and duplicate counts, incomplete processing and the outcome reason. Check it alongside the dataset when a run stops early or returns fewer results than requested.

Download your results

Open your run's dataset, choose Export and select JSON, CSV or Excel. JSON keeps nested fields together. CSV and Excel are useful when you want to review the records in a spreadsheet.

See Apify's download and export guide for the available formats and field options.

Pricing

Pay-per-event pricing uses a one-time start event at run initialization and an item event for each accepted listing row. Summary records are not listing rows.

See the live Pricing tab for current rates and account-tier discounts.

Tips for best results

• Start with a focused city or search URL and a small cap. Inspect the initial fields before expanding your sample.
• Keep original price and location text. Parsed currency and location values are conveniences rather than independent verification.
• Expect missing optional images and prices. No image or price value does not establish that a listing lacks one in every view.
• Inspect summary outcomes after short exports. Compare saved, skipped and duplicate counts and check incomplete processing.
• Keep identifiers and capture times in your own history. Separate runs do not remember prior IDs or generate change alerts.

Limits and caveats

Only public Marketplace views accessible without login are supported, without cookies, private messages or seller-contact extraction. Login redirects and access checkpoints can fail a run. Missing listings alone do not establish whether a target is private or deleted.

No discovered listings can produce an empty dataset with an expected_empty summary. Useful rows can remain after a later URL failure or processing limit. Inspect RUN-SUMMARY rather than assuming every URL completed.

Results are a bounded sample in discovery order, with duplicate IDs removed within a run. There are no separate keyword, radius, sorting or detail-extraction controls. The item cap is a ceiling rather than a guaranteed result count.

Only at most one image is returned. Seller names and IDs, description, creation time and live/pending/sold flags remain null, and reserved delivery/attribute fields remain empty. Individual listing inputs report details unavailable rather than adding enrichment.

Currency parsing recognizes dollar, euro and pound symbols. Dollar values are labeled USD without independent currency verification. There is no built-in inventory history, price-change detection or alert system.

Automation and integrations

Save your settings for next time

Once you have an input that works for you, save it as an Apify task. This keeps your settings together so you can use them again without filling in the form from scratch.

Run on a schedule

Need fresh results regularly? You can schedule the Actor or a saved task to run at a time that suits you.

Each scheduled run collects the data again. If you want to compare results or highlight changes, add that step in your own workflow.

Send results to your other tools

Use n8n, Make or Zapier to connect this scraper to the rest of your workflow. For example, you could pass its results to an AI assistant or add records to a spreadsheet. Follow the Apify integration guides for your chosen tool.

For a custom connection, an Apify webhook can notify your app when a run finishes or fails. Your app can then fetch the results or handle the failure.

API usage

Want to collect this data from your own app or automation? The examples below send input to the scraper and show how to collect its results.

The Node.js and Python examples wait for the run to finish before reading its results. The cURL example starts the run and returns its details. Wait for that run to finish, then use its defaultDatasetId to fetch the results.

For setup instructions, see Apify's JavaScript client guide, Python client guide and Actor runs API reference.

cURL

curl -X POST 'https://api.apify.com/v2/acts/fetch_cat~facebook-marketplace-scraper/runs' \
  -H "Authorization: Bearer $APIFY_TOKEN" \
  -H 'Content-Type: application/json' \
  --data @- <<'JSON'
{
  "startUrls": [
    {
      "url": "https://www.facebook.com/marketplace/nyc/search/?query=desk"
    }
  ],
  "maxItems": 5
}
JSON

Node.js

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('fetch_cat/facebook-marketplace-scraper').call({
  "startUrls": [
    {
      "url": "https://www.facebook.com/marketplace/nyc/search/?query=desk"
    }
  ],
  "maxItems": 5
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

Python

import os
from apify_client import ApifyClient

client = ApifyClient(os.environ['APIFY_TOKEN'])
run = client.actor('fetch_cat/facebook-marketplace-scraper').call(run_input={'startUrls': [{'url': 'https://www.facebook.com/marketplace/nyc/search/?query=desk'}], 'maxItems': 5})
print(client.dataset(run['defaultDatasetId']).list_items().items)

API usage notes

cURL starts a run asynchronously. Use the returned run ID to check completion and its defaultDatasetId to retrieve results.

MCP and AI agents

You can ask your AI assistant to collect data with Facebook Marketplace Scraper and help you work with the results. The scraper returns the data, and your assistant can then summarize it, compare records or prepare notes.

Connect your assistant through the Apify MCP server. MCP gives your assistant a way to find this scraper, run it and read the results. Follow the official setup and sign-in guide for your app.

Easier setup with an Apify plugin

If you use a supported coding assistant, the official Apify plugin can set up the connection for you. It connects your assistant to Apify and includes instructions for common tasks. Follow the guide for your particular app.

Use Apify AI in Console

Prefer to keep everything in Apify? Open Apify AI in Console and ask it to find Fetch Cat's Facebook Marketplace Scraper. You can describe the data you want and ask questions about the results.

Apify AI is currently in beta. It asks for confirmation before starting an Actor, and normal run charges apply.

Choose your assistant

• Claude and Claude Code (Anthropic): Apify setup guide.
• ChatGPT and Codex (OpenAI): Apify setup guides.
• Grok Bot (xAI): Apify plugin guide.
• Gemini CLI (Google): MCP server setup guide. Use the server URL below with the HTTP configuration supported by Gemini CLI.

Connect just this scraper

To keep your setup focused on this scraper, add this server configuration to a compatible MCP client:

{
  "mcpServers": {
    "apify": {
      "url": "https://mcp.apify.com?tools=fetch_cat/facebook-marketplace-scraper"
    }
  }
}

Sign in to Apify when your client asks. If your client uses a Bearer token instead, follow its setup guide and keep the token in its secure configuration. Configuration formats vary by app, so use the linked guide if your client needs a different format.

Use Apify's general server

Already connected to the general Apify MCP server at https://mcp.apify.com? You can use it to find this scraper without adding another server. Ask your assistant to use Facebook Marketplace Scraper by Fetch Cat, or give it the identifier fetch_cat/facebook-marketplace-scraper.

Your assistant can check the available settings and retrieve the results from the returned run. If the run is still working, it should follow that run rather than start it again. Both connection options use Apify's hosted service.

Example requests

• “Use Fetch Cat’s Facebook Marketplace Scraper to collect up to 5 visible desk listings from https://www.facebook.com/marketplace/nyc/search/?query=desk. Show titles, original price text, locations and listing links.”
• “Collect at most 5 visible listings from the public city/category Marketplace URL I provide. Keep IDs and collection times for comparison with my own sheet, and mark missing prices or images.”
• “Retrieve the visible listing record for the public Marketplace item URL I supply, with a one-item cap. Show its title, displayed price and source link without requesting seller contacts, a full description or availability flags.”

Normal Apify charges apply. Check the live Pricing tab before asking your assistant to run a larger batch.

Pay with x402

If your AI agent has a funded wallet, it can pay for Apify usage through x402. This experimental option lets an agent use Apify without a conventional account.

Apify AGI provides a prepaid API token with a spending cap after payment. Your agent can use that token to run this scraper through the Apify API or an authenticated MCP connection.

Some MCP setups also support paying for each request directly. That is a different payment option, so check the official guide for its availability.

Follow the official guide for wallet setup, supported payment options and current terms. Apify handles the payments. Keep wallet keys and payment tokens in your agent's secure configuration.

Other ways for agents to pay

Apify also supports MPP for prepaid access through AGI and Skyfire for eligible Actors. If your agent already uses one of these, see the agentic payment guide to choose the right setup.

FAQ

Can I use this as a Facebook Marketplace API?

You can call this scraper through Apify's API and retrieve its dataset. It is not an official Facebook API and does not provide private Marketplace access.

Can I export Facebook Marketplace data to CSV or Excel?

Yes. Open the run's dataset and choose CSV, Excel or JSON, or retrieve rows through the Apify API.

Does it require my Facebook account?

No. It only attempts logged-out public access and does not accept Facebook cookies or credentials.

Why are descriptions and seller fields empty?

These are reserved output fields, not currently extracted data. Other fields such as price, image and location can be missing when the public listing does not expose usable values.

Does it sort newest-first or find only new listings?

No. It collects visible listings in discovery order and removes duplicate IDs only within a run. It does not guarantee Facebook's ordering or compare against previous runs.

Related Actors

• Facebook Pages Scraper — Public business-page information.
• Facebook Ads Library Scraper — Research Facebook advertising.
• Google Maps Places Scraper — Find local business/place information.
• Craigslist Classifieds Scraper — Research classified listings on another marketplace.
• eBay Marketplace Scraper — Collect marketplace product information.

Support and feedback

For custom additions or integrations, email hello@fetchcat.dev.

Found an error or have a feature request? Open an issue with the run URL, a non-sensitive input example and what you expected.

Need help sharing it? See Apify’s guide to sharing a run when reporting an issue. Sharing a run can give the developer access to its input, logs and results, so use a run that contains no sensitive data. Please leave out API tokens, passwords, cookies, private documents and personal data. Use a public sample URL or a redacted example instead.

Tried this scraper? We'd love to hear how it worked for you. Leave a review to help others choose the right tool and help us improve it. Your feedback means a lot to us.

Made with care for curious people, AI agents and the possibilities in data. ♥