Skip to main content
GET
Marketplace Search
Search Facebook Marketplace by keyword in one location. Returns structured listings with price and currency, photos, place, condition subtitles, delivery types, sold/pending state and the seller actor. This endpoint reads Facebook’s public, logged-out Marketplace feed. No Facebook account is needed. Credits: 10

Authorization

string
required
Your ScrapeBadger API key.

Query Parameters

string
required
Search keywords, e.g. macbook pro.
string
default:"nyc"
A Facebook Marketplace location slug (nyc, la, london, newcastleupontyne) or a numeric Facebook place id (107486895947382). Human-readable names such as Durham, UK are not accepted and return a 400 — see Location targeting below.
integer
Search radius around the location, 1–500. With strict_filters=true, always kilometres: each returned listing is checked against Facebook’s approximate coordinates. Without verification, Facebook can silently widen the radius (its US UI uses miles).
integer
Minimum price, in the location’s currency.
integer
Maximum price, in the location’s currency.
integer
Only listings posted within the last N days, 1–30.
string
One of best_match, price_ascend, price_descend, distance_ascend, creation_time_descend.
string
Comma-separated. One or more of new, used_like_new, used_good, used_fair.
string
One of local_pick_up, shipping.
string
Pagination cursor — the end_cursor from a previous response.
boolean
default:"false"
Enforce radius, age and explicit price bounds locally. Requests with a radius fetch listing details; candidates without verifiable coordinates are excluded. Continuations use overlapping price ranges instead of Facebook’s empty logged-out cursor pages.
boolean
default:"false"
Include full public descriptions, photo URLs, seller and approximate coordinates. Enables verified search. Unavailable details are reported in search_info.

Verified search and daily monitoring

Pass the opaque end_cursor back as after, keeping all filters unchanged. Verified cursors expire after one hour and permit up to eight pages. An empty filtered page can still have useful continuations: follow has_next_page, not count. Each page is a separate API request at the current endpoint price. search_info.coverage is always partial. pagination=public_price_ranges means continuations explore narrower price ranges. Newest-first order applies within each page; sort the combined pages by creation_time_utc yourself. A finished continuation does not mean all matching Facebook listings were found. Facebook may delay public discovery, and dense searches can exceed these bounds. For daily collection, overlap the previous two days, search multiple validated UK place slugs or IDs, and deduplicate by listing ID across locations and runs. The runnable daily collector saves new listings in newest-first order and persists IDs in SQLite. Its --locations option accepts a comma-separated list. Schedule it daily in your own scheduler. This is a sampled public discovery feed, with no exhaustive-coverage or freshness SLA. search_info reports rejected old/out-of-radius candidates, duplicates and unreadable details. Detail failures or the request budget can reduce returned results. Coordinates are approximate; this verifies distance from the reported point, not an exact address.

Response

MarketplaceListing[]
Each MarketplaceListing includes id, title, custom_title, url, price_formatted, price_amount, amount_with_offset, strikethrough_price, min_price, max_price, currency, primary_photo, photos[], creation_time_utc, created_at, location_text, city, state, city_page_id, latitude, longitude, category_id, subtitles[], delivery_types[], attributes, is_sold, is_pending, is_live, is_hidden, seller and description.city_page_id is the canonical Facebook place id for the listing’s city, and can be passed straight back as a location.Without verification or detail enrichment, Facebook feed cards generally have no coordinates: latitude and longitude are null, and the listing’s place is carried by location_text, city, state and city_page_id. Coordinates come from /marketplace/item/{item_id}.
integer
Number of listings in this page.
string
Pass as after for the next page.
boolean
Whether more listings are reachable.
string
The query that was searched.
string
The location value you sent.
ResolvedLocation
The location Facebook actually searched: slug (the slug or place id it resolved to), latitude, longitude and radius. Check these against your own geography before ingesting the listings.

Location targeting

Facebook does not error on an unknown {location} — it silently searches a different place and returns HTTP 200. Which place depends on the exit the request went out on, so the same bad input can come back as San Francisco, Maryland or Delaware inventory. This endpoint compares the location Facebook echoes back against the one you asked for and returns a 400 invalid_location whenever they differ, so you are never billed for wrong-country inventory:
400 invalid_location
Only places Facebook itself has minted a slug for resolve: london and newcastleupontyne do, durham and sunderland do not. To cover a town with no slug, search a nearby location that does have one and read city_page_id off the listings — those numeric place ids are valid location values:
A location Facebook recognises echoes back verbatim in resolved_location.slug (newcastleupontyne → newcastleupontyne), so you can also assert the coordinates fall inside your target geography before ingesting.
Feed cards are truncated by Facebook: description, the full photos[] gallery and attributes are reliably populated only on /marketplace/item/{item_id}.

Example

Response
Use strict_filters=true with an overlapping two-day window for daily monitoring. Persist listing IDs, follow continuations and sort all collected pages before processing.