Facebook Marketplace (Vehicles) Data Parser & API
Facebook Marketplace is one of the largest C2C vehicle channels in the world — roughly 205M US Marketplace monthly active users — but it has no public listings API and sits behind a Meta login wall with heavy anti-bot defenses, so coverage is best-effort; Carapis can deliver what is feasible through one REST API. We are deliberately honest here: the reach is enormous, but the feasibility is the lowest of any platform in this catalog.
On request — not in the live feed today. We do not continuously crawl Facebook Marketplace (Vehicles) right now. Activation takes 2–3 weeks of engineering and is quoted per source, because each one ships with dedicated proxies, anti-bot tuning and ongoing maintenance. Ask us to add it.
| Country | Global |
|---|---|
| Type | Marketplace |
| Owner | Meta |
| Vehicle types | used, private, dealer, moto |
| Monthly visits | ~205M US Marketplace MAU |
| Active listings | massive (untracked) |
| API access | No public API (parse-only) |
| Parse priority | ★★☆☆☆ |
| Official site | www.facebook.com/marketplace |
What is Facebook Marketplace (Vehicles)?
Facebook Marketplace is Meta’s consumer classifieds product, and its Vehicles category is a primary C2C and dealer channel, especially in North America (~205M US Marketplace MAU). Listings are largely free-form: a price, photos, location and a seller-written description, with some structured fields (make, model, year, mileage). There is no official listings API, and access is gated by a login wall and behavioral anti-bot systems.
Market Position
By raw reach, Facebook Marketplace is among the biggest used-vehicle channels anywhere — ~205M US Marketplace MAU, and a primary outlet for private sellers and many dealers (Accio; Car Studio AI). But its data value is constrained by structure and access: fields are shallow and unstandardized, there is no API, and Meta’s login wall plus anti-bot defenses make systematic extraction hard and incomplete. The honest summary is high value in principle, low feasibility in practice — so Carapis treats coverage as best-effort rather than comprehensive.
What the API returns
Response schema
Indicative — this is the shape, not a guarantee. Every source returns the same structure, so what you build against does not change when you add one. Which fields carry a value depends on the source and on the individual listing: a site that does not publish mileage returns null there, and Facebook Marketplace (Vehicles) is no exception.
List — GET /apix/api/vehicles/ — returns 30 fields per vehicle:
idstringsource_codestringbrand_namestringbrand_slugstringmodel_namestringmodel_slugstringtrimstringyearintegerprice_usdintegermileageintegerfuel_typeFuelTypeEnumtransmissionTransmissionEnumbody_typeBodyTypeEnumcolorColorEnumseller_typeSellerTypeEnumregionstringsource_locationobjecthas_accidentbooleanis_new_vehiclebooleanis_verifiedbooleanstatusVehicleStatusEnumis_availablebooleanfirst_seen_atstringlast_seen_atstringthumbVehiclePhotophotosarrayphotos_countintegerhas_valuationbooleanhas_llm_analysisbooleananalysisobject
Detail — GET /apix/api/vehicles/{id}/ — adds 23 more:
generationstringprice_originalstringprice_original_currencystringoriginal_msrpstringengine_ccintegerseat_countintegerdrive_typeDriveTypeEnumhas_simple_repairbooleanhas_recallbooleanrecall_fulfilledbooleanwarranty_typestringinspection_passedbooleanowner_countintegeris_undervaluedbooleanvaluation_scorenumberfeaturesarraydescriptionstringlisting_urlstringlisting_idstringvinstringvehicle_nostringavailability_checked_atstringstatus_changed_atstring
Abbreviated example:
{
"id": "0193f2c1-...",
"source_code": "encar",
"brand_name": "BMW",
"model_name": "320i",
"trim": "M Sport",
"year": 2021,
"price_usd": 28400,
"price_original": "38900000",
"price_original_currency": "KRW",
"mileage": 45000,
"fuel_type": "gasoline",
"transmission": "automatic",
"has_accident": false,
"listing_url": "https://...",
"photos": [{ "url": "https://cdn.carapis.com/..." }],
"first_seen_at": "2026-09-28T11:04:22Z",
"is_available": true
}Which sources you can actually query is answered by GET /apix/api/sources/ with your API key — it is the list your account can pull today, and it is the one to trust over any page on this site.
Because Facebook Marketplace listings are seller-authored and largely unstructured, fields are shallower than on portals or auction sites, and completeness varies listing by listing. This is the least data-rich source in the catalog relative to effort — we flag that plainly rather than overstate coverage.
API Quick Start
Python
import requests
resp = requests.get(
"https://api.carapis.com/v2/listings",
params={"source": "facebook-marketplace", "limit": 20},
headers={"Authorization": f"Bearer {API_KEY}"},
)
for car in resp.json()["results"]:
print(car["make"], car["model"], car["year"], car["price"])Get an API key at my.carapis.com and see the full API reference. Pricing is on the pricing page .
Use Cases
- Market research — gauge private-seller pricing and supply signals in C2C-heavy markets, accepting best-effort coverage. See market research.
- Pricing intelligence — private-party asking prices complement dealer-sourced data for dealers.
- Import / export — limited, but private-seller listings can surface stock not on portals. See import & export.