Is there a Facebook Marketplace API for deal alerts?

No. Facebook does not publish a public, buyer-facing Facebook Marketplace API for deal alerts, saved-search webhooks, or listing pushes. Every serious tool checks Marketplace itself, then filters and notifies you outside Facebook's own system.

If you source for a living (many searches, many cities, first message wins), you are not shopping for JSON. You are shopping for detection plus filters. An "official Marketplace API" pitch for car alerts is a yellow flag until someone shows a public Facebook doc you can open.

What searchers usually want

"Facebook Marketplace API" almost always means one of three jobs:

1. Deal alerts: interrupt me when a matching listing appears
2. Data dumps: titles, prices, and links into a sheet or warehouse
3. Auto-contact: message sellers without opening Facebook

For resellers, job 1 is the money path. Job 2 is research. Job 3 is a different product and a different risk. Crawlbench automates detection and filtering, and never messages sellers. You send on Messenger, so your account stays safe.

What Facebook actually exposes

Facebook's public developer surface is built around Pages, ads, and business messaging, not a consumer Marketplace inventory feed for arbitrary buyers. There is no documented endpoint that says "new private-seller Tacomas under $28k in my cities every few minutes."

That gap filled with listing-export tools, desktop agents, browser extensions, hosted "Marketplace APIs" (listing-export tools with nicer docs), and alert services. None of them have a blessing Facebook published for buyer alerts. They check Marketplace and notify you.

Facebook also publishes no SLA for third-party tools. Pick one that someone keeps running.

Option A: DIY script or GitHub "API wrapper"

A script fetches Marketplace results and returns rows. It feels like an API because your code calls a function.

Fits: raw data, you can own breakage, missed hours are fine.

Fails: income depends on first-hour replies. Sessions and layouts break without notice. Keeping the pipe open becomes a part-time job (DIY upkeep). Full tradeoff: listing tool vs alert service.

Option B: Generic listing-export APIs

Third-party services sell HTTP access to pages they fetch. You point them at Marketplace URLs and parse JSON-ish output. Vendor blogs will call this "the Marketplace API."

Fits: occasional research pulls, price studies, one-off comps.

Fails: a live sourcing routine. You still need pass/fail filters (make, model, year, exclusions), dedup, recency, and a phone interrupt. Per-request pricing also hurts when you check many profiles often.

Option C: A Marketplace-specific alert service

An alert service owns the reseller workflow: Marketplace checks, structured filters, a reason on every alert, alerts on Telegram, email, or an in-app queue. Crawlbench works this way: it checks busy cities every 10 minutes on Starter, every 5 on Growth, every 2 on Pro and every minute on Scale, as pricing shows on 18 October 2026.

Fits: time-to-first-message on inventory you actually buy.

Plus: every alert says why it passed, with a price comparison against similar active listings.

Tool shapes: monitoring tools list. Labor vs software when volume grows: operator vs software.

How to evaluate any "Marketplace API" pitch

Ask in plain language:

• Public Facebook doc URL, or your own polling layer?
• How fast does an alert reach me, in every city I cover?
• Filters before the alert, or every new row?
• Who fixes breakage when Marketplace changes?
• Auto-message sellers? (Default answer for someone who sources daily: no.)

Safe automation stops at detection and filtering. Messaging stays human (bot safety).

A one-week test

Pick one hot model across the cities you actually cover. For seven days, log:

1. When you first saw the listing (or when a tool alerted you)
2. Post time, if Facebook shows one
3. Whether you would have messaged it

You do not need unpublished ranking rules. You need your latency baseline. If native Notify Me is late on that model, an "API" that cannot send you a filtered alert on a schedule you know will not help.

Who should still build a listing-export pipe

Build when your product is data: pricing models, research dumps, internal catalogs. Maintenance is cost of goods.

Do not build when your product is "message the seller first across dozens of searches." That work needs frequent checks, filters that kill junk, and an alert people answer. Confusing those jobs is how engineering weekends eat sourcing weeks.

Bottom line

There is no buyer-facing Facebook Marketplace API for deal alerts. Buy the outcome: raw data you maintain, or filtered alerts someone else keeps alive. Crawlbench is the second path (match reasons and Marketplace coverage). Your time stays on Messenger, not on pretending an official feed exists.