Resale Radar

Hear about a resale ticket before someone else buys it.

Sold-out parties trade their spare tickets on TicketSwap, and a listed ticket is usually gone within a couple of minutes. Resale Radar keeps the event’s page open in your own Chrome, reads it at a random interval you choose, and the moment a ticket is listed it rings your Mac, emails you and pushes to your phone.

Chrome on macOS, open source · 2026JavaScript · Chrome extension · Python

Resale Radar’s dashboard: the watcher is working, the last check found 0 available, 3 sold and 134 wanted, with tiles for the typical gap, alerts, failures and missed tickets above a table of every check

How it works

It reads the page the way you would.

There is no API to ask. The event page itself says how many tickets are listed, so Resale Radar keeps reading it.

01

A pinned tab, not a scraper

It loads the event page in your own Chrome, the way you would press refresh, and reads the one line that matters: how many tickets are available, sold and wanted.

02

At a random pace

Each check books the next at a random moment between your minimum and maximum. New installs wait two to four minutes, so it never hammers the page.

03

It knows when to stop

Each event stops being checked the morning after it happens, and its tab closes. Nothing keeps running for a party that is over.

Alerts

When a ticket appears, everything goes off at once.

Each channel can be switched off on its own, and tested on its own, silently.

Your Mac rings

The volume goes up, a siren and a voice take turns, and a Stop button stays on screen. Your own volume comes back afterwards.

Chrome jumps to it

A notification, and the event’s tab comes to the front, ready for you to buy.

An email

Sent from your own Gmail, with an app password that lives in the macOS Keychain and nowhere else.

Your phone buzzes

A push through ntfy, to a private topic only you know.

Why it has to be fast

One ticket came up, and it was gone in under two and a half minutes.

Watching one sold-out club night: more than 160 people wanted a ticket, and the only one listed in the first 29 hours sold before the next check. Seconds matter, so everything goes off at once.

160+people wanting a ticket
1ticket listed in 29 hours
142 sat most, from listed to sold

Dashboard

Every check, and what went wrong.

A dashboard lists every check with how long it took and what the page said, counts the tickets that sold between two checks, and explains anything odd in plain words. A control panel next to it sets everything else.

Resale Radar’s controls: the random wait between checks with presets, pause buttons, the event being watched and when to stop, which alerts fire, and the alarm’s volume and length

Back-off

When the site says slow down, it slows down.

It never tries to get around a check. It waits, tells you why, and comes back by itself.

A verification check
Stops and asks you to finish it yourself.
“Too many refreshes”
Pauses 15 minutes, then 30, then an hour, and resumes on its own.
Three failures in a row
Waits 5, 10, then 20 minutes and longer before trying again.
After the event
Stops checking and closes its tab.

Leave the page alone. It will call you.

For Google Chrome on macOS. Open source under MIT. Not affiliated with TicketSwap: use it within their terms, and keep the interval gentle.