Most Vinted alert services send you a push notification or an email. That works fine when you're buying the odd pair of trainers for yourself. But if you're running a reselling operation — or even just tracking a dozen searches across multiple markets — you probably want something that feeds directly into whatever system you already use.
That's what webhooks do. Instead of you checking for alerts, the alert comes to your code.
What is a webhook, exactly?
A webhook is an HTTP request that a server sends to your URL every time something happens. In Vinotify's case, the "something" is: new items matched one of your search alerts.
When the monitoring system finds fresh Vinted listings that match your search filters, it fires a POST request to the URL you've configured. The body is JSON and contains the search name, item titles, brands, prices, conditions, sizes, Vinted links, and photo URLs — everything you'd see in the email or push notification, but in a format a machine can parse.
Here's a simplified example of what the payload looks like:
{
"event": "new_items",
"search_id": 42,
"search_name": "Nike Dunk Low",
"item_count": 3,
"items": [
{
"title": "Nike Dunk Low Panda 42",
"brand": "Nike",
"size": "42",
"condition": "Very good",
"price": "55.00",
"url": "https://www.vinted.fr/items/...",
"photo": "https://..."
}
]
}You can do whatever you want with that data once it arrives. Log it, forward it, filter it, act on it.
How it works in Vinotify
Webhooks are part of the Pro plan. When you create a search alert on Pro, Vinotify generates a unique webhook secret for that search. You can then:
- Poll the latest payload — there's a dedicated GET endpoint that returns the most recent webhook data for your search, authenticated by the secret. No JWT needed, so it's easy to call from a cron job or a Google Apps Script.
- Set an external URL — point Vinotify at your own HTTPS endpoint (a Zapier webhook, an AWS Lambda function URL, a Make.com scenario, a self-hosted server — anything). Vinotify will POST matching items there every time new ones appear.
Both options are available from the API. You can find your webhook secret and configure the external URL through the search settings.
Practical setups that actually work
Knowing webhooks exist is one thing. Knowing what to do with them is another. Here are a few setups that Vinotify Pro users have put together:
1. Google Sheets inventory tracker
Deploy a free Google Apps Script that accepts POST requests and appends each item to a spreadsheet. Columns for title, brand, price, condition, URL. You get a running log of every item your alerts catch, sortable and searchable, without any paid tools.
This is probably the simplest starting point. You write about 20 lines of JavaScript in Apps Script, publish it as a web app, and paste the URL into Vinotify.
2. Telegram or Discord bot
If you'd rather get alerts in a group chat instead of (or alongside) push and email, set up a small relay. Receive the webhook, format it into a message with the item photo and a "Buy now" link, and post it to a Telegram channel via the Bot API or a Discord channel via its webhook URL. A single serverless function handles this.
3. Price-drop filter
Say you're tracking a broad search — "North Face Nuptse" across all sizes. That might surface 15 new listings a day, but you only care when something lands below €80. Your webhook receiver checks the price field and only forwards items under your threshold. The rest get silently logged.
4. Multi-market dashboard
Pro supports multi-market searches (FR, DE, IT, UK, etc. from a single alert). Webhook payloads include the search name and item URLs, which contain the market domain. A lightweight dashboard that collects webhook deliveries from several searches gives you a single view across markets and categories — useful if you're sourcing inventory at scale.
Using webhooks as a "safe autocop"
Some resellers want the speed of autocop tools without the risk of handing over login details or getting banned. Webhooks make this possible:
- Configure a webhook on your Pro search that targets a small script or serverless function.
- When new items match, your script receives the data instantly — including the direct Vinted URL for each item.
- Your automation sends you an instant notification (Telegram, SMS, desktop popup) with the item link ready to open.
- You tap the link and buy manually — with a normal account, at normal human speed.
This gives you near-instant awareness of new listings without any bot touching your Vinted account. No credentials shared, no ban risk, and much cheaper than dedicated autocop subscriptions.
Read more: Vinted Autocop Tools vs Webhooks: Why Alerts Beat Auto-Buyers →
Polling vs. push: which to choose
Vinotify offers both. If your use case tolerates a small delay (batch processing, spreadsheets, analytics), polling the GET endpoint on a schedule is simpler — no server needed, and you can do it from a browser extension, a GitHub Action, or a cron tab.
If you want real-time delivery the moment items match, set an external URL and let Vinotify push to you. This is better for bots, live dashboards, and anything where a 30-second head start matters.
A few things to keep in mind
- Treat your webhook secret like a password. Anyone with it can read your search results. Don't commit it to a public repo.
- External URLs must be HTTPS (or HTTP for local development). Vinotify won't deliver to non-HTTP schemes.
- Payloads cap at 50 items per delivery. If a single check finds more matches, the payload contains the first 50. This keeps request sizes sensible for downstream services.
- Delivery is best-effort. If your endpoint is down or returns an error, the payload is still cached and available via the polling endpoint for 24 hours. There's no automatic retry queue — keep your receiver reliable or use the poll endpoint as a fallback.
Getting started
If you're already on the Pro plan, every search you create has a webhook secret. Head to your search settings, grab the secret, and either poll the latest-payload endpoint or set an external URL.
If you're on Free, Plus, or Premium, webhooks aren't included — but push notifications and email cover most personal use cases well. Webhooks make sense when you want to do something programmatic with the data, not just see it.
Frequently asked questions
- How do I set a webhook URL in Vinotify?
- Each Pro search has its own webhook secret. Set the destination that receives deliveries with PUT /api/v1/searches/{search_id}/webhook/external-url, sending the URL in the body. Send an empty string to stop delivery. The destination must be a public HTTPS endpoint.
- What does the webhook payload look like?
- Vinotify POSTs a JSON body with event set to new_items, plus search_id, search_name, item_count, and an items array holding the matching listings.
- Are failed webhook deliveries retried?
- No. Push delivery is best effort and there is no retry queue, so respond quickly and queue the work on your side. If your endpoint was down, the most recent payload stays available for 24 hours at /api/v1/searches/{search_id}/webhook/latest, and the event feed keeps 48 hours of history behind a cursor.
- Can I point the webhook straight at a Discord channel?
- Not directly. The Vinotify payload is not in Discord's incoming-webhook format, so a small bot or bridge has to translate it before posting.
- Which plan includes webhooks?
- Webhooks are a Pro plan feature.