Dashboards and trackers
Add new listings or price changes to an internal buying, inventory, or research view.
Webhook alerts
Send new marketplace listing alerts to your tools with webhooks.
Turn Facebook Marketplace and other supported search matches into signed JSON for a dashboard, tracker, team workflow, or automation you control. Signed webhooks are included during the free trial and on paid plans with no separate add-on fee or mobile app requirement.
Facebook Marketplace webhook alerts
Monitor the search, then send each useful Facebook match to your endpoint
Create a Facebook Marketplace search in Classifindr, choose its keywords, picked locality, price, category, condition, rules, and check speed, then assign a webhook channel. When a check finds a new match or a tracked listing drops in price, Classifindr sends the signed event to your HTTPS receiver.
This is a Classifindr alert channel, not an official Facebook webhook. It does not require Facebook credentials. Facebook controls the approximate default area and the public results returned around the locality you select.
Set up Facebook Marketplace webhook alertsSupported search sources
Webhook delivery works as a channel for supported Classifindr searches across Auto Trader, CarGurus, Cazoo, Facebook Marketplace, Gumtree, Craigslist, Trade Me, Kijiji, OfferUp, Poshmark, Pinkbike, Vinted, eBay, Mercari, and Chrono24.
Each marketplace keeps its own search controls and availability. The webhook receives matches after Classifindr checks and filters the saved search.
Send matches to dashboards and automations
Webhooks are useful when an alert needs to become part of a workflow, not just another notification.
Team workflows
Send the same structured alert to a shared process so people can review and act together.
Your own automations
Trigger the next step in a tool you control after Classifindr finds a match.
Two useful events
Receive new listings and price-drop alerts
Each payload includes the search, match, price, source listing link, and optional cached thumbnail needed for your workflow. Search location can include locality, state or region, country, and postcode fields when known. Listing location is optional and may be only a display value such as city and state. Latitude, longitude, and distance from the search locality are not sent. Listing text is preserved as supplied by the marketplace and bounded for size.
New listing matches
Receive the listing, search, match reason, and source link when a check finds a new match.
Price decreases
Track a listing that drops in price with its previous and current prices.
CloudEvents JSON
{
"type": "alert.listing.matched.v1",
"id": "wh_01JEXAMPLE",
"subject": "match_123",
"data": {
"schema_version": 1,
"listing": { "title": "Example camera", "price": "450.00", "currency": "USD" },
"change": { "type": "new_listing" }
}
}Simple setup
How to set up webhook alerts
- 01
Create an endpoint in the web portal.
- 02
Save the whsec_ secret when it is shown once.
- 03
Verify the endpoint with a signed test event.
- 04
Assign the webhook to the searches you choose.
- 05
Review delivery history and redeliver when needed.
For receivers
Set up from a desktop browser
Create and verify a webhook in the desktop web portal, save the one-time whsec_ secret, then assign the active channel to your searches. Mobile can view and assign existing active webhooks, but setup and delivery management stay on the desktop web app.
If you prefer an API, the tenant endpoints are under /api/v1/webhook-endpoints. The published schemas and receiver examples below are the reference contract.
What your receiver should do
- 1. Accept `POST` requests over HTTPS and read the raw UTF-8 body.
- 2. Verify `Webhook-Id`, `Webhook-Timestamp`, and every `v1` signature before parsing JSON.
- 3. Reject timestamps outside five minutes and deduplicate by `Webhook-Id`.
- 4. Return a 2xx response quickly, then process the event asynchronously.
Webhook security and delivery status
- Signed HTTPS requests: verify the raw request body with the one-time secret before processing it.
- Retries with visibility: temporary failures are retried, delivery attempts are recorded for 30 days, and repeated failures can pause an endpoint.
- At least once and unordered: deduplicate by
Webhook-Idand do not depend on event order.
- Secret rotation: rotate a secret from the portal without exposing the old value in responses.
- Web-only management: create, verify, rotate, inspect, and redeliver from the web portal. Mobile can view and assign active webhooks.
- Reachability, not ownership: a 2xx verification response proves signed reachability. Use only an endpoint you are allowed to configure.
For receivers
Return a 2xx response quickly, process asynchronously, allow a five-minute timestamp tolerance, and keep a processed-event record keyed by Webhook-Id.
Webhook guides
Webhook setup examples
Start with the guide that matches the next decision, from one Facebook Marketplace search to a durable team integration.
Facebook Marketplace webhook alerts
Create the search, connect the endpoint, understand the payload, and troubleshoot the delivery path.
Open Facebook Marketplace webhook alertsSecure webhook receiver guide
Verify raw-body signatures, reject replay, deduplicate events, and acknowledge requests quickly.
Open Secure webhook receiver guideWebhooks vs push and email
Choose whether a person, a system, or both should receive each marketplace match.
Open Webhooks vs push and emailReseller and buying-team workflow
Route new listings and price decreases into sourcing queues without removing human review.
Open Reseller and buying-team workflowMarketplace webhook alert questions
Can I receive Facebook Marketplace alerts as webhooks?
Yes. Create the Facebook Marketplace search in Classifindr, create and verify a webhook in the desktop portal, then assign that webhook channel to the search.
Which events are available?
V1 sends signed new-listing match and price-decrease events as versioned CloudEvents JSON.
Can the same search send a phone alert and a webhook?
Yes. Assign more than one channel when a person and a system both need the match.
Do webhooks require Facebook or marketplace credentials?
No. Classifindr does not ask for or store marketplace login credentials.
What happens when my endpoint fails?
Temporary failures are retried. The desktop portal keeps delivery history for 30 days, shows safe failure reasons, and supports manual redelivery.