Ticketmaster bots are software, or software-assisted setups run by people, that buy tickets faster or in larger quantities than one fan could. Most are run by resellers, which is why they are also called ticket scalping bots. A ticket bot can be as small as a script that refreshes an event page or as large as a stack of hundreds of accounts, payment cards, IP addresses, and parallel browser sessions.
At covered US events, the federal BOTS Act prohibits circumventing technical controls that enforce posted purchase limits or protect posted purchasing-order rules. It separately covers selling or offering those tickets in interstate commerce when the seller participated in the violation, could control it, or knew or should have known how the tickets were obtained.
This guide covers what ticket bots actually do, what the BOTS Act says, how it has been enforced from 2021 to November 2026, how Ticketmaster detects bots, and where proxies fit. It is a plain-language explainer, not legal advice.
What Ticketmaster bots are
"Ticket bot" covers several different tools, and the legal risk differs between them. The four types you'll run into:
- Drop monitors and alerts. A script watches an event page or an API and pings a person on Discord, Telegram, or email when tickets appear or prices drop. A human still buys.
- Single-session purchase automation. A browser userscript or Selenium script that refreshes until the buy button appears, picks seats, adds them to the cart, and sometimes fills in the login and checkout forms.
- Multi-account purchase stacks. The same automation run across many accounts at once, each with its own payment card, phone number, IP address, and browser profile, sometimes with a CAPTCHA-solving extension. This is what resellers mean by a bot farm.
- Human-run multi-session setups. No purchase automation at all: staff working in anti-detect or "multi-session" browsers, each window logged into a different account behind a different IP. The FTC's 2026 cases against Elite Events and REPS describe this kind of setup.
The BOTS Act: what it actually prohibits
The Better Online Ticket Sales Act became law on December 14, 2016, and is codified at 15 U.S.C. 45c. It makes two things unlawful.
The first, subparagraph (a)(1)(A), is to "circumvent a security measure, access control system, or other technological control or measure on an Internet website or online service that is used by the ticket issuer to enforce posted event ticket purchasing limits or to maintain the integrity of posted online ticket purchasing order rules."
Subparagraph (a)(1)(B) covers selling or offering such tickets in interstate commerce if the seller participated in the violation, had the ability to control it, or knew or should have known the tickets were acquired in violation.
A few details matter in practice:
- A safeguard is covered when the issuer uses it to enforce a posted ticket limit or maintain a posted online purchasing-order rule.
- Covered events are open to the public, take place at venues holding more than 200 people, and are promoted or generally ticketed in interstate commerce.
- It doesn't ban resale. Reselling tickets you bought within the rules is a matter of state law and the platform's terms. Whether ticket scalping is legal varies by state.
- There are two exceptions. Building or using software to investigate or enforce against violations, and security research into these controls "to advance the state of knowledge in the field of computer system security or to assist in the development of computer security product."
Enforcement runs through the FTC, which treats a violation as a breach of a trade regulation rule, and through state attorneys general. A knowing rule violation carries a civil penalty of up to $53,088 per violation under the FTC's January 2025 inflation adjustment, and a September 2026 notice keeps that amount unchanged for 2026. Cases involve thousands of purchases, so judgments run into the millions.
BOTS Act enforcement from 2021 to 2026
The FTC brought its first cases in 2021. The broker cases below describe IP masking among the alleged tactics. A complaint records allegations. A settlement or court order records the outcome.
| Case | Date | What was alleged | Status |
|---|---|---|---|
| Three New York brokers (first cases) | January 2021 | About 150,000 tickets bought with automated software, "software to conceal their IP addresses", and "hundreds of fictitious Ticketmaster accounts and credit cards" | Settled: about $31 million in judgments, $3.7 million payable |
| FTC v. Key Investment Group (ruling) | Filed August 2025 | Thousands of accounts, thousands of card numbers, spoofed IP addresses and phone numbers; at least 379,776 tickets for nearly $57 million in about a year | Motion to dismiss denied April 2026 |
| FTC and seven states v. Live Nation and Ticketmaster (filing) | September 2025 | Ticketmaster let brokers exceed posted limits; five brokers controlled 6,345 accounts holding 246,407 concert tickets | Motion to dismiss denied in September 2026; Ticketmaster denies violating the Act |
| FTC v. Elite Events (complaint) | July 2026 | The FTC alleged the broker exceeded posted purchase limits at more than 2,400 events | The entered order suspended all but $300,000 of the $10.758 million judgment upon payment |
| United States v. REPS & Company (complaint) | October 2026 | 18.5 million tickets for $1.3 billion across at least 83,500 events, using thousands of accounts, "proxy IP addresses and multi-session browsers" | Pending; REPS says "We never use bots" |
Two 2026 rulings matter for anyone who reads the Act as covering only automated bots.
In the Key Investment Group case, Pollstar reported that the broker argued it couldn't be charged because it used "digital tools with human users, rather than 'bots.'" Judge George L. Russell III of the District of Maryland disagreed: "The statute unambiguously applies to 'any person' and not just to 'bots.'"
In the Live Nation case, Judge Maame Ewusi-Mensah Frimpong of the Central District of California rejected the argument that a ticketing platform can't be liable: "The BOTS Act does not preclude platforms from facing liability, and the Court will not read it as doing so." Neither ruling finds anyone liable. Both let the cases proceed.
The Elite Events order bars the defendants from using multiple accounts or using multiple IP addresses simultaneously on a single device to circumvent ticket limits.
Bills that would expand the BOTS Act
The MAIN Event Ticketing Act (H.R. 2713) cleared the House Energy and Commerce Committee 36-0 on September 16, 2026. It would require ticket issuers to maintain controls that enforce their limits, report known circumvention to the FTC within 30 days, and set minimum penalties for violations. Its Senate companion, S. 196, is on the Senate calendar. As of November 2026 neither has passed a floor vote, so neither is law.
Outside the US
The UK's Breaching of Limits on Ticket Sales Regulations 2018 make it an offence to use software designed to complete any part of a ticket purchase "with intent to obtain tickets in excess of the sales limit, with a view to any person obtaining financial gain." It applies to UK events even when the buyer acts from abroad, and the fine is unlimited in England and Wales and up to £50,000 in Scotland. Other countries have their own rules. Check the law where the event takes place.
Ticketmaster bot detection: what the platform checks
Ticketmaster documents several safeguards. A shopping recommendation alone does not establish that a fan circumvented a technical control covered by the Act.
Registration before the sale. Verified Fan asks fans to register in advance. Ticketmaster's Eras Tour explainer describes it as "identifying real humans and weeding out bots". It also says that for the November 2022 presale, "the staggering number of bot attacks as well as fans who didn't have codes" produced "3.5 billion total system requests – 4x our previous peak."
Posted ticket limits. Event organizers can set a per-event limit, and Ticketmaster's ticket limit article says it "is posted during the purchase process and is verified with every transaction." It adds that multiple accounts may not be used to exceed it, and that the limit covers "accounts or orders associated with the same name, email address, billing address, credit card number or other information." These are the "posted event ticket purchasing limits" the BOTS Act protects.
Account rules. Ticketmaster's Terms of Use require each account to be "linked to a unique individual" and ban duplicate accounts. The code of conduct bans bots and automated purchasing, circumventing security measures, and attempts to "Manipulate any identifiers or disguise the origin of any interaction". It also bans attempts to conceal your identity "by using multiple Internet Protocol addresses ... to conduct transactions". Its paused or suspended article asks fans to "Stay within one browser window and on a single device while shopping", which is the habit a multi-session browser breaks.
Network checks. Ticketmaster's error message help article says a VPN, iCloud Private Relay, or similar tool can trigger a block by making it look like you're using multiple IPs. Proxy and data-center IP ranges get the same treatment from most anti-bot systems. Our anonymous proxy detected guide explains how sites classify IPs.
Identity checks. Ticketmaster uses Persona for selfie and ID checks. Its security check article explains why the biometric data is kept for up to 7 days: deleting it instantly "would mean we could not tell when the same person tries to enter a sale again through different accounts." That check targets the multi-account setup directly.
Human checks. reCAPTCHA prompts and browser challenges filter out simple scripts.
The FTC alleges that Ticketmaster allowed some brokers to exceed posted limits. Ticketmaster disputes the allegations.
Where proxies fit legally around ticketing
A proxy only changes which IP address a site sees. The BOTS Act doesn't mention proxies, and routing traffic through one is legal. The law cares about what the proxy is used for. Ticketmaster's Terms are stricter than the statute, because they ban disguising the origin of any interaction, not only purchases over the limit.
So the line falls in two places. Using proxies to run extra accounts, sessions, or purchases past a posted limit is the conduct in the FTC's cases. Ticketmaster prohibits concealing your identity or disguising where a transaction comes from. Even a personal VPN can trigger a block. Outside of buying, proxies fit a few jobs:
| Use | Where proxies fit | Status |
|---|---|---|
| Running several accounts or sessions to beat a ticket limit | The FTC cites IP masking in its complaints | Can violate the BOTS Act if it bypasses a technical control enforcing a posted limit at a covered event |
| Buying on Ticketmaster through any proxy or VPN | Changes the IP Ticketmaster sees | Can trigger a block. Disguising the origin of a transaction violates the Terms |
| Finding events and scheduled sale dates | Not needed | Use the Discovery API, which has a default quota of 5,000 calls per day at 5 requests per second |
| Price research on other resale marketplaces | Regional price checks and stable egress | Depends on each marketplace's terms; see whether data scraping is legal |
| A ticket issuer or venue testing its own site | Checking geo-restrictions, regional pricing, and how pages render from consumer networks | Authorized by the site owner |
| Investigating fake ticket sites, phishing, or scam ads | Seeing region-targeted pages the way a victim would | Viewing a suspected scam without circumventing ticket purchase controls falls outside this prohibition |
| Security research on purchase controls | Reproducing what an attacker sees | (a)(2)(B) exception, but get the platform's written permission, because other laws and the Terms still apply |
For the monitoring jobs, pace requests to what the source allows. The delay calculator works out how many requests per minute a given delay produces.
That is also our honest product fit. Our residential proxies suit geo-QA and public-data monitoring on sites that permit it. We don't recommend any proxy, ours included, for buying on Ticketmaster. If you're comparing proxies with VPNs for privacy rather than ticketing, see proxy server vs VPN.
Retail bots sit in a different legal spot. No federal law like the BOTS Act covers sneakers or other retail drops. The main risks there are the store's terms and cancelled orders, which our Refract bot guide and sneaker proxies guide cover. Don't carry a retail bot setup over to event tickets and assume the same rules apply.
FAQ
Are Ticketmaster bots illegal?
At covered events, the BOTS Act prohibits circumventing controls that enforce posted ticket limits or maintain posted online purchasing-order rules. It also restricts selling or offering tickets obtained through prohibited circumvention in interstate commerce if the seller participated, had the ability to control the violation, or knew or should have known how the tickets were obtained.
Is it illegal to use a proxy to buy tickets?
The proxy itself isn't illegal. Using proxies to buy more tickets than the posted limit, across extra accounts or sessions, is the conduct the FTC charged in the Elite Events and REPS cases. Ticketmaster prohibits disguising the origin of an interaction. Its help center recommends disconnecting a VPN if it triggers a block.
Can Ticketmaster detect bots?
Ticketmaster checks several layers: Verified Fan registration, ticket limits checked on every transaction, one-person-per-account rules, VPN and proxy detection, Persona selfie and ID checks, and reCAPTCHA. The Persona data is kept for up to 7 days specifically to catch one person entering a sale through several accounts. No layer is perfect, but together they cover each part of a multi-account setup.
What is the penalty for using ticket bots?
Under the BOTS Act, the FTC can seek up to $53,088 per violation for knowing violations, and state attorneys general can sue too. Real judgments have ranged from about $31 million across three brokers in 2021 to more than $10.7 million against one broker in 2026, though most of each was suspended for inability to pay. Ticketmaster can separately cancel orders and close accounts.
Does the BOTS Act cover small shows?
Only if the venue holds more than 200 people, the event is open to the general public, and it's marketed or ticketed across state lines. Most concerts, sports games, and theater shows sold through Ticketmaster meet that bar.
Are ticket drop alert bots legal?
An alert that tells a person tickets are available doesn't get around a purchase limit, so on its own it falls outside the BOTS Act. How you collect the data still matters. Ticketmaster's Discovery API lists events and sale dates. Near-real-time primary inventory status requires authorized access to the separate Inventory Status API.
Conclusion
Ticketmaster bots can monitor a sale or automate purchases. At covered events, the BOTS Act prohibits bypassing technical controls that enforce posted limits or purchasing-order rules. For event announcements, use published sale dates. For a purchase, use your own account and follow the event’s posted limits.
