Ticketmaster UK

Which links work, what the monitor reads, and what suppressed means.

Ticketmaster UK is one of the two platforms Firm Monitors watches; the other is the football clubs on eticketing.co.uk. This page is what is specific to Ticketmaster: which links work, what the monitor actually reads, and the two words the site uses that confuse people. Everything here — the three-second interval, the anonymous read, the cleared session — is about this site, not about the clubs.

Paste any event URL

Open the event on ticketmaster.co.uk and copy the address bar. Anything of this shape works, with or without query parameters:

https://www.ticketmaster.co.uk/arsenal-v-chelsea-london-14-03-2026/event/3W00A1B2C3D4E5F6
https://www.ticketmaster.co.uk/event/3W00A1B2C3D4E5F6

The part that matters is the segment after /event/: that is the event id, and it is what the monitor watches. The words before it are the site's own slug and we ignore them. When you paste a link the wizard shows you the platform and the event id it extracted before anything starts, offline — no request is made to the site at that point, so a bad paste costs nothing.

These do not work, and the wizard will say so:

Artist, venue, tour or search pages — there is no single event to watch.
ticketmaster.com, .ie, .de and the rest. Only .co.uk today.
A secure.ticketmaster.co.uk checkout deep link. Use the event page.

What the monitor reads

It asks the site the same question the "quick picks" panel on the event page asks: for this event, at this quantity, what is on sale right now. The answer is a list of picks, each of which becomes a line on your card:

Primary picks — tickets sold by the box office.
Resale picks — tickets listed by other fans. These carry a direct link to that listing, which the card includes.

The Markets setting on the monitor picks which of those you want: all, primary or resale. Start on all and narrow it if the channel is too noisy.

Quantity matters more than it looks. The site answers the question "can I buy N together", so a quantity of 4 will not report a pair. If you would take any pair, set 2; if you need four seats together, set 4 and accept fewer cards.

"Suppressed" and "lowDemand"

Two words from the site's own page data that turn up in support questions.

suppressed: The event's own page state when the site has nothing to show you. In our testing, an event marked suppressed answered our read with an empty list at every quantity we tried, and its own page agreed — it showed nothing either. Treat it as sold out, or availability hidden. It is not an error, and it is not the monitor failing.
lowDemand: The site's own description of how the event is selling. It is a label, not a restriction, and it has no effect on whether you get a card.

A suppressed event is still worth watching. That is the case a monitor is for: the page has nothing today, and you want to know the second it has something. Whether a suppressed event that later restocks announces itself in this feed has not been confirmed here, so treat it as watched, not proven.

The anti-bot check

Before it can read anything, the monitor has to pass the site's anti-bot check and get a cleared session. That costs one credit and takes about seven to twelve seconds. The session then reads the event repeatedly until the site retires it — in our testing that was usually about 20 minutes at the default interval, occasionally only a few — at which point the monitor gets a new one automatically. You see this on the monitor card as the Session age ticking up and resetting, and in the activity feed as Session checked.

Some exits are refused the moment a new session is first used, even though the challenge was answered correctly. The monitor treats that as a bad exit, drops it and tries another. A handful of those per hour is normal; a monitor that never gets past it needs different proxies. See blocked exits.

Ticketmaster UK is on Firm credits only

Ticketmaster UK accepts only the Firm solver at the moment — your own CapSolver key is not used here. The new-monitor page does not offer the choice for this platform, and monitors here always spend Firm credits.

This comes from our testing, not a policy. In our testing CapSolver tokens are almost always refused here — the site passes the check and then refuses the session the first time it is used — so we don't recommend it at the moment. The Firm solver is what we recommend and what we test against. We have not been able to test KagedCap yet, so we can't recommend it either.

A key you have already added stays on your account and is used on any platform that accepts one. If vendor tokens start being accepted on Ticketmaster UK we will turn the choice back on. See captcha keys and credits.

Interval

Three seconds per event is the default and the floor. At that rate one event is twenty reads a minute, which a cleared session sustains. Pushing harder does not find tickets sooner — it gets the session refused, and a refused session finds nothing at all until it has spent another credit. The longer answer.

Several events at once

One monitor watches one event. There is no combined mode, and there does not need to be: each monitor keeps its own counters, its own log and its own webhook, so a noisy event cannot bury a quiet one. If several of your monitors watch the same site they may share a cleared session behind the scenes, which is cheaper for you in credits and is handled for you.

Buying is still you

Firm Monitors reports availability. It does not hold, reserve, add to basket or buy, and it never signs in to your Ticketmaster account. When a card arrives, open the event yourself. That is also why eligibility — presale codes, memberships, ticket limits — lives on your account and not on our alert.

← Reading an alert card AXS →

Something here wrong or missing? Tell us, and we will fix the page rather than just answer the message.