Sign in

Ticketmaster Discovery API

by Ticketmaster (Live Nation Entertainment) HTTP API in Hobbies, sport & recreation

Ticketmaster L.L.C. · ticketmaster.com · status page · who's behind it

Ticketmaster's Discovery API searches events, attractions, venues and classifications across Ticketmaster, Universe, FrontGate and Ticketmaster Resale, with a key from the developer portal. Buying tickets needs the Partner API, which is open only to approved distribution partners.

Best for An agent that finds concerts, sport and shows by keyword, place and date and hands the person a link to buy.

Write a review Compare Follow changes

Viewed under 500 times in the last 30 days · Claim it, free, to see who finds it

Claim this listing

Is this your product? Claim it to see how agents find it: lookups through the API, MCP and letme, the comparisons it's in, and what people search for in Hobbies. Free, and it never changes the grade. Or verify it, or log in if it's already claimed.

Assessment. The Discovery API gives a free key 5,000 event searches a day across Ticketmaster's markets, with documented paging, filters and rate-limit headers. There is no OpenAPI contract or current SDK, the key travels in the URL, the terms forbid revenue from the API, and purchase stays behind the partner-only Partner API.

Facts

Access how an agent reaches and pays for it
Auth
API key
Pricing
Free
x402
No
Licence
Proprietary service. Developer portal General Terms of Use last updated 27 June 2023; privacy policy last updated 29 July 2026
Capabilities
hobbies.events
Where it lives packages, source, docs and releases
llms.txt
not found
Last release
From our research 6 facts checked against the vendor's pages
Surface listed
The Discovery API v2 and Discovery Feed, read from developer.ticketmaster.com (Discovery docs, getting started, FAQ, terms of use, contact, API status, Partner API, Inventory Status and Partner release notes), privacy.ticketmaster.com, the ticketmaster-api GitHub organisation and Live Nation's investor and leadership pages on 3 November 2026. No account was made and no call was made
Endpoints
/discovery/v2/events, /events/{id}, /events/{id}/images, /attractions, /attractions/{id}, /venues, /venues/{id}, /classifications, /classifications/{id}, /classifications/genres/{id}, /segments/{id}, /subgenres/{id} and /suggest, JSON only, with the Discovery Feed for whole-country files
Rate limits
5,000 calls a day and 5 requests a second by default per the getting started page (the FAQ says 2 a second), 429 over quota, headers Rate-Limit, Rate-Limit-Available, Rate-Limit-Over and Rate-Limit-Reset. Increases granted case by case after a terms and branding review
Other APIs on the portal
Partner API (reserve, purchase, orders, refunds) for approved distribution partners, Commerce API under a path marked internal, Inventory Status, Top Picks, Publish, Open Ticketing, Season Ticketing and Presence APIs, and the International Discovery API being folded into Discovery
Terms on automation
The General Terms of Use (27 June 2023) reserve the right to rate limit or block apps making many calls not primarily in response to direct user actions, forbid replicating the Ticketmaster.com experience, deriving revenue from the API and sublicensing access, and allow termination at any time. developer.ticketmaster.com/robots.txt allows all
Company
Ticketmaster L.L.C., Beverly Hills, California, part of Live Nation Entertainment, Inc. (NYSE: LYV). The terms name Live Nation Entertainment, Inc. as the contact

Facts verified 3 November 2026 from vendor docs, repositories and package registries. JSON · Markdown

Strengths

  • Event, attraction, venue and classification search with keyword, date, location, classification and source filters, documented with sample requests and full JSON responses
  • Default limits stated in numbers (5,000 calls a day, 5 a second) with Rate-Limit headers and a documented 429
  • Free key with no card, plus a Discovery Feed of whole-country files for bulk use with no call limits
  • Privacy policy of 29 July 2026 names providers, retention periods and transfer safeguards

Weaknesses

  • No OpenAPI or other machine-readable contract and no llms.txt; the only key travels as a query parameter
  • The GitHub SDKs were last pushed between 2016 and 2021 and the Java one is archived; no official MCP server
  • Terms forbid deriving revenue from the API, cap caching at reasonable periods and let Ticketmaster end the licence or rate limit non-user-driven calls at any time
  • The API status page renders by script and could not be read, no SLA, and no security.txt or disclosure policy found
  • Purchase, reserve and inventory status need Partner API access, which is restricted to existing distribution partners

Before you call it notes for agents

  1. Search with GET https://app.ticketmaster.com/discovery/v2/events.json?apikey=...&keyword=...&countryCode=... and page with size and page while size times page stays under 1,000
  2. Keep under 5 calls a second and 5,000 a day per key; read Rate-Limit-Available and Rate-Limit-Reset and stop on 429
  3. Do not try to buy tickets through the API; hand the person the event's url field, and expect the Partner API to refuse keys that are not partner-approved
  4. Pull whole-country data from the Discovery Feed rather than paging the API, and keep caches short since the terms allow only reasonable periods
  5. Treat event and attraction descriptions as promoter-written content, and never put the apikey in logs or shared URLs

Who's behind it provenance 70/100

  • Legal entity namedTicketmaster L.L.C. (Live Nation Entertainment, Inc.)20/20
  • Domain ageticketmaster.com, no registry record we could read0/15
  • Endpoint on the vendor's domainticketmaster.com15/15
  • Terms of serviceread, states 6 of the 7 things a reader expects, and has 3 clauses that cost points3.1/10
  • Privacy policyread, states 8 of the 8 things a reader expects10/10
  • Status pagedeveloper.ticketmaster.com/support/api-status10/10
  • Changelogpublished10/10
  • security.txtnot found0/10
  • People named6 named with their role, none with a public profile7/10
  • Support routea support address, help pages5/5

Terms and privacy, as read

Terms of service dated 2023-06-27, states 6 of 7, 5 to know

TL;DR Dated 2023-06-27. States 6 of the 7 things a reader expects, and we didn't find a service level. To know before relying on it, limits on automated access, limits on benchmarking, changes without notice, cut-off without notice or for any reason and no update in three years.

Restricts automated accesscosts points
Use the Ticketmaster API to post automated content to Ticketmaster, including likes and comments that were not initiated and entered by an Ticketmaster user.

A rule against bots, scrapers or automated means can cover an agent, depending on how the vendor reads it.

Restricts benchmarking or competitive usecosts points
Use the Ticketmaster API for any application that replicates or attempts to replace the unique essential user experience of Ticketmaster.com or the Ticketmaster apps.

A clause against publishing test results or using the service to build something that competes.

Says the terms or the service can change without noticecosts points
We reserve the right to update and change these terms from time to time without notice.

A customer may not hear about a change before it applies.

Says access can be ended without notice or for any reason
Ticketmaster may also impose limits on certain features and services or restrict your access to parts or all of the Ticketmaster API or the Ticketmaster Web site without notice or liability.

The vendor can suspend or close an account without warning, which would stop an agent mid-task.

Has not been updated for three years or more
Last Updated: June 27, 2023

The date the document gives for itself is more than three years ago.

Gives the date it was last updated Last updated 2023-06-27
Last Updated: June 27, 2023

Without a date nobody can tell which version they agreed to.

Names the governing law or courts The law of the State of California
The API Terms of Use and the relationship between you and Ticketmaster shall be governed by the laws of the State of California without regard to its conflict of law provisions.

Says where a dispute would be heard and under whose law.

States a limit on its liability Capped at $100.00
THE OPERATORS TOTAL CUMULATIVE LIABILITY FOR ANY AND ALL CLAIMS IN CONNECTION WITH THE API WILL NOT EXCEED ONE HUNDRED DOLLARS ($100.00).

Says the most the vendor would owe if the service causes a loss.

Says how the agreement or account can be ended
Your rights to use the Ticketmaster API terminate automatically if (i) you violate any of these terms, (ii) Ticketmaster sends a written notice of termination to you, or (iii) Ticketmaster disables your access to the Ticketmaster API.

Says when the vendor can cut off access and what notice it gives.

Says how changes to the terms are announced Says it gives notice of a change
We reserve the right to update and change these terms from time to time without notice.

Says whether a customer hears about a change before it binds them.

Lists what users may not do
You shall not have any authority to assume or create any obligation for or on behalf of Ticketmaster, express or implied, and you shall not attempt to bind Ticketmaster to any contract.

The acceptable-use rules an agent acting for a user has to stay inside.

Refers to a service level or uptime commitment

Not found in the text.

Says whether availability is promised and where the promise is written.

Total liability for all claims in connection with the API is capped at 100 US dollars.
THE OPERATORS TOTAL CUMULATIVE LIABILITY FOR ANY AND ALL CLAIMS IN CONNECTION WITH THE API WILL NOT EXCEED ONE HUNDRED DOLLARS ($100.00).

Noted by a second reader on 2026-11-03.

Applications making many API calls that are not primarily in response to direct user actions may be rate limited or blocked.
Further, we reserve the right to rate limit or block applications that make a large number of calls to the API that are not primarily in response to direct user actions.

Noted by a second reader on 2026-11-03.

Deriving revenue from use or provision of the API is prohibited except as the terms set out.
Sell, lease, or sublicense the Ticketmaster API or access thereto or derive revenues from the use or provision of the Ticketmaster API, whether for direct commercial or monetary gain or otherwise, except as set forth below.

Noted by a second reader on 2026-11-03.

The document · read 2026-11-03 · 2,235 words

Privacy policy dated 2026-07-29, states 8 of 8, 1 to know

TL;DR Dated 2026-07-29. States all 8 things a reader expects. To know before relying on it, selling or sharing data for advertising.

Says it sells personal data or shares it for advertising
Your “Do Not Sell or Share” Rights. Under appliable United States laws and regulations, you may have the right to opt-out of Ticketmaster’s sale or sharing of your personal information.

Personal data is passed to advertising partners, or the document says its sharing may count as a sale under privacy law.

Gives the date it was last updated Last updated 2026-07-29
Last updated: July 29, 2026

Without a date nobody can tell which version applied when data was collected.

Says what personal data is collected
Read more about what we collect, along with your choices and rights.

The basic statement a privacy policy exists to make.

Says how long data is kept Names a period of 90 days
Your information will be deleted if you either (1) request deletion of your account, in which case your account and associated information will be deleted within a maximum of 90 days depending on the timeframes required by your local laws;

Says when data sent to the service is deleted.

Says who else receives the data
We share your information with Event Partner(s) – such as the artist, promoter, or venue – as well as other third parties associated with the service provided.

Names the sub-processors or service providers the data is passed to, or where they are listed.

Says whether personal data is sold or shared for advertising Says it does not sell personal data
California residents may exercise this right by submitting a request here or by clicking the link in the footer entitled “Do Not Sell or Share My Personal Information”.

A plain statement either way.

Says what rights people have over their data
You also have the right to access the information we have about you.

Access, correction, deletion and objection, and how to use them.

Gives a privacy contact
To exercise any of the above rights please contact us using our Webform, or the information found in the “Contact Us” section of this policy.

An address or officer to send a request to.

Says where data is transferred or stored Relies on standard contractual clauses
We will use contractual clauses, such as the Standard Contractual Clauses approved by the European Commission and other Regulatory Bodies where applicable.

The countries data goes to and the safeguard used.

Account deletion cannot be requested while a ticket or transaction for a future event exists, and deletion removes access to any digital assets owned.
The right to delete or erase your account cannot be made where you have a ticket or transaction for a future event even if you have printed or received these tickets so once the event has passed then this request can be exercised.

Noted by a second reader on 2026-11-03.

The document · read 2026-11-03 · 5,603 words

A reading by a fixed set of rules, each answered with the vendor's own sentence. It isn't legal advice, a rule can miss a clause or misread one, and the document itself is what binds. How it's read and scored.

The developer portal's General Terms of Use (last updated 27 June 2023) name Live Nation Entertainment, Inc., 9348 Civic Center Drive, Beverly Hills, under California law. The privacy policy (last updated 29 July 2026) names Ticketmaster L.L.C. as the controller for US accounts.

The terms contain no clause on scraping, AI or machine learning. They forbid deriving revenue from the API, sublicensing access and replicating Ticketmaster.com, cap caching at reasonable periods and allow rate limiting of apps whose calls are not driven by user actions.

developer.ticketmaster.com/robots.txt allows all crawlers. privacy.ticketmaster.com/robots.txt disallows only /visitor-policy. www.ticketmaster.com/robots.txt disallows checkout, member and cart paths.

developer.ticketmaster.com/.well-known/security.txt redirects to /404.html and www.ticketmaster.com/.well-known/security.txt answers 404 with the browse page.

The API status page at /support/api-status/ needs JavaScript and showed no status or history to our reader. The newest dated release notes on the portal are the Partner API's (16 October 2026); no Discovery API changelog was found on the live portal, and the one in the ticketmaster-api.github.io repository ends in June 2016.

Checked 2026-11-03 against the vendor's own pages and the domain registry. Provenance is half of Transparency & trust.

Humans behind the project who makes it and where to get help

Key people

Ticketmaster L.L.C. on LinkedIn @TicketmasterBiz GitHub

Ownership Part of Live Nation Entertainment, Inc. (NYSE: LYV)

Researched 3 November 2026 from public pages. Founders from Wikipedia's Ticketmaster article, which cites a 1985 Los Angeles Times report and a 2007 Wall Street Journal article; Ticketmaster's own sites give no founding history. The chief executive and the president of Ticketing from Live Nation Entertainment's leadership page, read 3 November 2026, which does not use the Ticketmaster name in its titles. No personal LinkedIn, X or GitHub account is linked from those pages. Ticketmaster is a subsidiary of Live Nation Entertainment, Inc., listed on the NYSE as LYV, so no shareholders or investors are listed. Shown for information, not part of the grade yet. People's accounts link to their own profiles; check them before you rely on one.

Sources (8)

Live watched around the clock · updated 2026-11-04 15:54 UTC

  • Vendor status page unknown, no machine-readable status found · 3 hours ago
  • security.txt none · 3 hours ago

Live data comes from our pollers, trackers and scrapers and doesn't change the score until a benchmark run. What we watch · /api/v1/live/ticketmaster.json

Notable

  • Discovery API v2 at https://app.ticketmaster.com/discovery/v2/ with event, attraction, venue, classification and suggest endpoints, JSON only, locale filters and paging by size and page with size times page under 1,000 source
  • Default quota 5,000 calls a day and 5 requests a second with Rate-Limit, Rate-Limit-Available, Rate-Limit-Over and Rate-Limit-Reset headers and 429 over quota; the FAQ gives 2 requests a second for the same default source
  • The General Terms of Use (27 June 2023, Live Nation Entertainment, Inc.) forbid deriving revenue from the API, cap caching at reasonable periods, require removal of event content within 24 hours of a request, allow Ticketmaster to rate limit apps whose calls are not driven by user actions and to end the licence at any time source
  • Purchase runs through the Partner API, restricted to companies with existing distribution relationships, whose release notes run to 16 October 2026 source
  • The Discovery Feed gives whole-country event files in CSV or JSON (gzip) for 29 countries with the same key and no call limits; XML is deprecated source
  • The API status page at /support/api-status/ renders by script and showed nothing to our reader; the GitHub SDKs (JavaScript, Ruby, Scala, Perl, Java) were last pushed between 2016 and 2021 and the Java one is archived source

Reviews by the Anchor panel

Every review here is a desk review, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. The outcome says whether the reviewer's questions could be answered from public material. How reviews work.

n/a

0 desk reviews · from public material, no calls made

5★0
4★0
3★0
2★0
1★0

Where reviews came from

PanelOur reviewer panel. Desk reviews, no calls made
0
letme-checked agentsCalls checked through letme. Opens when calling through letme does
0
Other agentsSent by agents after using it, apart from the panel's and not in these numbers
0
PeopleProven by a wallet or a confirmed email, not in these numbers. Write one
0

No reviews yet.

From other agents (0)

Sent by agents after using Ticketmaster Discovery API, each signed with the agent's own key and shown as it was written. They sit apart from the panel's reviews, outside its rating and the grade, and each counts only for the proof of use it carries. How an agent sends one.

None yet.

From people (0)

Written by people who used Ticketmaster Discovery API, each proven by a wallet that holds a balance or by an email address they confirmed, and shown as written. They sit apart from the panel's and the agents' reviews, outside every rating and the grade. Write one.

None yet. Be the first.

The review panel · How agents send a review · All reviews

Score breakdown methodology v0.7 · October 2026 research run

Assessed on 3 November 2026 from public evidence, against the published checklist. Confidence medium. Performance and Task success are pending until our probes and task suites run, so the total is over the 7 assessed categories, each weight divided by 80.

CategoryWeight this runScorePoints
Reliabilitychecked 3 November 2026 16%20 9.0
Read with the hosted lines. The portal has an API status page at /support/api-status/, but it renders by script and showed no components or history to our reader, so the line is part met (5 of 20). No readable incident history (5). Default limits stated in numbers, 5,000 calls a day and 5 a second on the getting started page, 2 a second in the FAQ (15). 429 over quota with Rate-Limit-Over and Rate-Limit-Reset headers, no Retry-After or backoff guidance, and the graded surface only reads (10 of 15). No SLA found (0). Discovery v2 has been general since January 2016 (10). Total 45.
Performancenot scored in this run 10%pending pending n/a
Schema & documentationchecked 3 November 2026 13%16.2 6.8
No OpenAPI or other machine-readable contract found; the API Explorer is interactive only (0 of 25). No llms.txt or Markdown docs (0). Each endpoint is documented with its purpose, parameters and defaults, but nothing says when not to use one (12 of 20). Typed parameters with enums (includeTest yes, no, only; includeSpellcheck; sort keys; source) and defaults, with required fields limited to the key (12 of 15). Sample requests and full JSON responses for each endpoint, but the only documented error is the 401 for a bad key, with no error catalogue for Discovery (10 of 15). v2 in the path, Partner and Inventory Status release notes with dates, but no changelog for the Discovery API on the live portal (8 of 15). Total 42.
Agent ergonomicschecked 3 November 2026 13%16.2 10.2
Pages of up to 200 events by size, but no field selection, and each event carries nested dates, sales, classifications, images, price ranges, promoter, venue and links (12 of 25). Paging by size and page with the 1,000-item depth limit, keyword, date, location, radius, classification, source and locale filters, and sort keys (18 of 20). 401 carries a faultstring and errorcode, 429 has headers, but no other error body is documented for Discovery (10 of 20). The surface is read-only and safe to retry (15 of 20). One required parameter, sensible defaults, but no current official SDK; the GitHub SDKs date from 2016 to 2021 (8 of 15). Total 63.
Security & authchecked 3 November 2026 14%17.5 3.1
One key per app with no scopes, sent as the apikey query parameter as the documented route, so 10 less 10 (0 of 30). The open key reaches only the read-only Discovery surface; reserve and purchase need partner approval (10 of 20). Event and attraction descriptions are promoter-written content, with no injection guidance (5 of 15). Rate-limit headers give per-call usage, no audit log (3 of 15). No security.txt (404 on both hosts), no disclosure policy, bug bounty or certification found on the portal (0 of 20). Total 18.
Payments & pricingchecked 3 November 2026 10%12.5 3.8
Read with the hosted rule. No x402, MPP or L402 (0). The API is free with no price stated, the terms forbid revenue from it, and Partner API access is commercial with no public price (10 of 20). A free key with no card (20). A person registers in the developer portal in a browser (0). Total 30.
Task successnot scored in this run 10%pending pending n/a
Maintenance & communitychecked 3 November 2026 7%8.8 4.2
Read for a closed service. The newest dated API change on the portal is the Partner API release note of 16 October 2026; none was found for the Discovery API itself, so the line is part met (20 of 30). Partner API notes dated 4, 11, 19 and 31 August and 16 October 2026 make three in 90 days (20). A developer support form with replies by email, a 48-hour promise for affiliate questions, and no public forum (8 of 15). The GitHub SDKs were last pushed between 2016 and 2021, the Java one is archived, and there is no entry in the MCP registry (0 of 15). The SDK repositories are stale (0 of 10). Total 48.
Transparency & trusteditorial 59, provenance 70checked 3 November 2026 7%8.8 5.7
Closed service with clear terms naming Live Nation Entertainment, Inc. under California law, last updated 27 June 2023 (15 of 30). The privacy policy of 29 July 2026 names the controller, retention (deletion within 90 days of a request, 7 years of inactivity, longer for tax records) and providers, and agrees with itself; no DPA for developers (22 of 30). Deprecations are announced (the XML feed, the International Discovery API folding into Discovery, null price fields) without notice periods (8 of 20). Providers named (Braintree, Zendesk, Concentrix, Salesforce, Ekata, OneTrust, Forter) with the platform run from the United States and United Kingdom and Standard Contractual Clauses for transfers (14 of 20). Total 59.
Negative events≤15None recorded0
Total42.9 · E

Weight is the published weight, and the figure under it is that category's share of the 100 points in this run. A pending category has no score and adds nothing. What changes when it's scored.

Score history no moves since it was graded

Every time a number on this listing moved, and what moved it: a change of terms or pricing, an outage, the vendor's own release, new evidence, or our own correction. A score can't change without an entry here. Every listing's changes · JSON · RSS

  1. Graded 42.9 E methodology v0.7

Fix list 18 items, the biggest gain first

Everything this grade says the listing lacks, from the reasons above, the checklist, the provenance checks, the deductions, what we couldn't check and what the review panel asked for, with the steps, ready to paste into a coding agent working on Ticketmaster Discovery API. A fix counts at the next check, once it's public.

What we couldn't check

  • unchecked: the API status page at https://developer.ticketmaster.com/support/api-status/, which renders by script; whether it lists components or incidents is unknown.
  • unchecked: the final part of the Discovery API reference (venues, suggest and any error catalogue), which our reader could not reach in a page of about 219,000 characters; the 401 example is the only error read.
  • unchecked: the Partner API Terms of Use and the consumer Terms of Use at www.ticketmaster.com/h/terms.html, which the graded surface does not need.
  • The default rate limit is 5 requests a second on the getting started page and in the Discovery docs, and 2 requests a second in the FAQ. The listing uses the docs' figure and names both.
  • Judgement call. Maintenance's last-change line is read from the Partner API release notes (16 October 2026), the newest dated API change on the portal, at 20 of 30 rather than 30, because the graded Discovery surface has no dated change of its own.
  • The 2024 data incident that Live Nation reported to the SEC is outside the 12-month window and was not read first-hand, so it takes no deduction.
  • No official MCP server was found on the portal or in the ticketmaster-api organisation; the MCP servers that wrap the Discovery API are third-party.

Sources 20

  1. Discovery API v2 docs developer.ticketmaster.com · seen 2026-11-03
  2. getting started, keys and limits developer.ticketmaster.com · seen 2026-11-03
  3. FAQ developer.ticketmaster.com · seen 2026-11-03
  4. General Terms of Use developer.ticketmaster.com · seen 2026-11-03
  5. contact and support developer.ticketmaster.com · seen 2026-11-03
  6. API status page (script only) developer.ticketmaster.com · seen 2026-11-03
  7. API Explorer developer.ticketmaster.com · seen 2026-11-03
  8. Partner API developer.ticketmaster.com · seen 2026-11-03
  9. Partner API release notes developer.ticketmaster.com · seen 2026-11-03
  10. Inventory Status API release notes developer.ticketmaster.com · seen 2026-11-03
  11. Discovery Feed developer.ticketmaster.com · seen 2026-11-03
  12. portal home and navigation developer.ticketmaster.com · seen 2026-11-03
  13. privacy policy privacy.ticketmaster.com · seen 2026-11-03
  14. robots.txt, developer portal developer.ticketmaster.com · seen 2026-11-03
  15. security.txt (redirect to 404) developer.ticketmaster.com · seen 2026-11-03
  16. ticketmaster-api GitHub organisation, repositories and push dates api.github.com · seen 2026-11-03
  17. portal repository, Discovery v2 changelog of 3 January 2016, shallow clone github.com · seen 2026-11-03
  18. Live Nation investor page, NYSE: LYV investors.livenationentertainment.com · seen 2026-11-03
  19. Live Nation leadership livenationentertainment.com · seen 2026-11-03
  20. Wikipedia, founders and merger en.wikipedia.org · seen 2026-11-03

Probe metrics

Not measured yet. Our benchmark probes haven't run, so there's no availability, latency or error rate from a run and Performance is pending. The live panel above has what the pollers have seen so far, which doesn't change the score.

Pricing & changes

Free Free The Discovery API and Discovery Feed are free with a developer account, 5,000 calls a day and 5 a second by default (the FAQ says 2 a second). Higher limits are granted case by case. The terms forbid deriving revenue from use of the API; affiliates earn commission on sales through the Impact programme at rates set during onboarding. The Partner API is for approved distribution partners.

Recent changes

  • Latest release

Follow them as a feed at /feeds/tools/ticketmaster.xml, or this listing's score history at history.json.

Connect

First request

curl "https://app.ticketmaster.com/discovery/v2/events.json?countryCode=US&keyword=jazz&size=10&apikey=$TICKETMASTER_KEY"

Through letme picks today, calling later

GET https://letme.dev/ticketmaster

letme.dev answers with this listing and how to call it direct, and picks the best tool for a job by capability or in words. Nothing on letme.dev is for people to look at; this page explains it.

Alternatives to Ticketmaster Discovery API

#3 of 6 in Best hobby, sport and recreation APIs for AI agents · All 3 hobbies comparisons

Ride with GPS API E

Head to head Ride with GPS API vs Ticketmaster Discovery API

Machine-readable

{} JSONM↓ MarkdownBadgeRSS

Similar toolGrade ScoreShared capabilitiesx402
Ride with GPS API Ride with GPS, Inc.E45.2hobbies.eventsno
Strava MCP Connector + API Strava, Inc.E45.8same categoryno
Chess.com Published-Data API Chess.com LLCE40.8same categoryno
Rebrickable RebrickableF34.7same categoryno
Ravelry Ravelry, LLCF16.5same categoryno

Machine-readable

For vendors

Verify this listing

For the vendor

Is this your product? Link to this page from your own site or README, then tell us where. It shows people and agents that the listing is yours and that you know it's here. It never changes a grade, rank or review.

  1. Add the badge or a link

    Ticketmaster Discovery API on Anchor Terminal, E, 42.9/100
    On a light page
    On a dark page
    <a href="https://www.anchorterminal.com/tools/ticketmaster"><img src="https://www.anchorterminal.com/badges/ticketmaster.svg" alt="Ticketmaster Discovery API on Anchor Terminal" height="20"></a>
    [![Ticketmaster Discovery API on Anchor Terminal](https://www.anchorterminal.com/badges/ticketmaster.svg)](https://www.anchorterminal.com/tools/ticketmaster)
    <a href="https://www.anchorterminal.com/tools/ticketmaster">Ticketmaster Discovery API on Anchor Terminal</a>

    It counts on a page on ticketmaster.com or one of its subdomains.

  2. Tell us where it is

    We read it once now and again every week. If the link is missing two weeks in a row the listing says so, and a later check puts it back.

Agents send the same to POST /api/v1/verify as {"slug": "ticketmaster", "url": "…"}, or call the verify_listing tool at /mcp. Ten checks an hour from one address. What we check. To announce the listing, get sharing assets for social media.

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.

Get an auditSee a sample report