Facebook Marketplace Scraper

Collect structured listings from Facebook Marketplace search pages and turn them into clean, analysis-ready dataset items.

This actor is designed for users who want a practical way to capture Marketplace results without having to manually copy titles, prices, images, locations, and listing metadata. It works across many listing categories, including vehicles, electronics, household items, and general local marketplace searches.

Overview

Facebook Marketplace search pages can show a lot of useful information, but the exact fields available vary from listing to listing. This actor gathers the listing data that is visible in the page content and normalizes it into structured JSON so you can sort, filter, export, or enrich it later.

The output is especially useful when you need to:

• compare prices across similar listings
• collect multiple search pages into one dataset
• archive listings before they disappear
• analyze marketplace inventory over time
• build internal tools around local resale data

What You Get

Each dataset item represents one listing. A listing can include the following fields:

• id
• url
• title
• price
• description
• location
• images
• videos
• seller
• category
• condition
• creation_time
• is_live
• is_sold
• is_pending
• delivery_options
• accessibility_captions
• sourceUrl

Some categories expose additional fields too. For example, vehicle listings may include fields such as:

• marketplace_listing_category_name
• marketplace_listing_leaf_vt_category_name
• custom_title
• custom_sub_titles_with_rendering_flags
• marketplace_listing_virtual_taxonomy_category

Because Marketplace content varies, not every item will contain every field. That is normal. The actor keeps whatever listing data is available and leaves missing values out or empty.

Input

Add one or more Facebook Marketplace search URLs to the Marketplace Search URLs field.

Available Settings

• Marketplace Search URLs: one or more search URLs to scrape
• Maximum Listings per URL: maximum number of items to collect from each search URL
• Fetch Detailed Information: enrich each listing with more fields when available
• Get New Items: prioritize newer listings by adjusting how results are collected

Input Behavior

• Each URL is processed separately.
• Results are collected per search URL, not as one shared pool.
• The sourceUrl field in each result shows which search page produced that listing.
• The actor accepts the search URL exactly as you copy it from Facebook Marketplace.

Output Format

The actor saves results to the default dataset as structured JSON objects.

Common Fields

id

The unique Marketplace listing identifier.

url

Direct link to the listing page.

title

The listing title, such as a vehicle model or product name.

price

A structured price object, usually containing:

• formatted
• amount
• currency

location

Location details extracted from the listing, which may include:

• city
• state
• country
• full
• latitude
• longitude

images

An array of image URLs found for the listing.

description

The listing description when available.

seller

Seller information when exposed by the listing page.

category

Category identifier or category-related metadata.

condition

Condition such as USED or similar Marketplace values.

creation_time

Listing creation time in a structured format.

is_live, is_sold, is_pending

Status flags that help identify whether a listing is active, sold, or pending.

sourceUrl

The search URL that produced the item.

Example Output

Here is an example of the kind of result this actor can produce:

{
  "id": "978087241456986",
  "url": "https://www.facebook.com/marketplace/item/978087241456986/",
  "title": "2023 Kia Niro Wind FWD",
  "price": {
    "amount": "22415.0",
    "currency": "USD",
    "formatted": "$22,415"
  },
  "location": {
    "city": "San Leandro",
    "state": "CA",
    "country": "US",
    "latitude": 37.713317871094,
    "longitude": -122.15148925781
  },
  "images": [
    "https://example.com/image-1.jpg",
    "https://example.com/image-2.jpg"
  ],
  "condition": "USED",
  "is_live": true,
  "is_sold": false,
  "is_pending": false,
  "sourceUrl": "https://www.facebook.com/marketplace/sanfrancisco/search?...",
  "custom_title": "2023 Kia niro wind fwd"
}

Typical Use Cases

• track used car listings in a target city
• monitor a search page for new inventory
• collect product listings for pricing research
• build a lead list from public Marketplace search results
• save historical data for later comparison

How To Use It

1. Paste one or more Facebook Marketplace search URLs into the input.
2. Set the number of listings you want from each search URL.
3. Enable detailed fetching if you want richer listing records.
4. Run the actor and open the dataset after completion.
5. Export the output in your preferred format.

Best Practices

• Use focused search URLs instead of very broad searches.
• Keep your search scope aligned with the number of results you need.
• Turn on detailed fetching when you need more than a quick summary.
• Use category-specific searches when you want cleaner, more relevant output.

Data Notes

• Some listings include more fields than others.
• Missing values are normal and depend on the search page and the listing itself.
• The output structure may vary by category.
• The sourceUrl field is helpful when you combine multiple searches in one run.

Example Fields You Might See

Depending on the listing, output may include extra fields such as:

• marketplace_listing_category_name
• marketplace_listing_leaf_vt_category_name
• custom_sub_titles_with_rendering_flags
• delivery_options
• accessibility_captions
• listing_video
• delivery_types
• marketplace_listing_virtual_taxonomy_category

These fields are included when Marketplace exposes them for the specific item.

Tips For Better Results

• Choose search URLs that already contain the filters you want.
• Focus each run on a specific city, category, or product type.
• Review the sourceUrl field if you need to trace a record back to its search page.
• Use the dataset export if you want to process the results in another tool.

Limitations

• Marketplace listings vary a lot, so output is not identical for every item.
• Some listings have only basic fields, while others expose richer details.
• Images, descriptions, and seller information depend on what is visible in the listing data.