{ "data": { "similar": [ { "grade": "E", "json": "https://www.anchorterminal.com/tools/ride-with-gps.json", "name": "Ride with GPS API", "score": 45.2, "shared": [ "hobbies.events" ], "slug": "ride-with-gps" }, { "grade": "E", "json": "https://www.anchorterminal.com/tools/strava.json", "name": "Strava MCP Connector + API", "score": 45.8, "shared": null, "slug": "strava" }, { "grade": "E", "json": "https://www.anchorterminal.com/tools/chess-com.json", "name": "Chess.com Published-Data API", "score": 40.8, "shared": null, "slug": "chess-com" }, { "grade": "F", "json": "https://www.anchorterminal.com/tools/rebrickable.json", "name": "Rebrickable", "score": 34.7, "shared": null, "slug": "rebrickable" }, { "grade": "F", "json": "https://www.anchorterminal.com/tools/ravelry.json", "name": "Ravelry", "score": 16.5, "shared": null, "slug": "ravelry" } ], "tool": { "slug": "ticketmaster", "name": "Ticketmaster Discovery API", "vendor": "Ticketmaster (Live Nation Entertainment)", "vendorUrl": "https://developer.ticketmaster.com", "kind": "http-api", "category": "hobbies", "summary": "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.", "url": "https://www.anchorterminal.com/tools/ticketmaster", "markdownUrl": "https://www.anchorterminal.com/tools/ticketmaster.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/ticketmaster.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/ticketmaster.json", "dns": "ticketmaster.grade.anchorterminal.com", "repo": "https://github.com/ticketmaster-api", "license": "Proprietary service. Developer portal General Terms of Use last updated 27 June 2023; privacy policy last updated 29 July 2026", "transports": [], "packages": [], "auth": "api-key", "authNotes": "One API key per application, registered in the developer portal after a browser signup, sent as the `apikey` query parameter on every request. The Partner API also accepts an `x-api-key` header. No scopes, expiry or rotation documented. A missing or invalid key returns 401 with errorcode oauth.v2.InvalidApiKey.", "pricing": "free", "pricingNotes": "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.", "priceSummary": "Free", "where": "local", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the Discovery API docs, getting started, FAQ or terms (checked 2026-11-03).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-11-03" }, "docsUrl": "https://developer.ticketmaster.com/products-and-docs/apis/discovery-api/v2/", "capabilities": [ "hobbies.events" ], "tags": [ "hosted", "closed-source", "api-key", "free", "free-tier", "no-card", "partner-only" ], "lastRelease": "2026-10-16", "graded": true, "anchor": { "graded": true, "score": 42.9, "grade": "E", "agentReady": false, "rank": 1176, "ranked": true, "rankOf": 1349, "categoryRank": 3, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 63, "maintenance": 48, "payments": 30, "reliability": 45, "schema": 42, "security": 18, "transparency": 65 }, "pending": [ "performance", "tasks" ], "breakdown": [ { "key": "reliability", "name": "Reliability", "weight": 16, "effectiveWeight": 20, "score": 45, "points": 9, "reason": "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.", "checked": "2026-11-03" }, { "key": "performance", "name": "Performance", "weight": 10, "effectiveWeight": 0, "pending": true, "points": 0, "reason": "Pending. Latency is measured per call by our probes, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until the first probe window closes." }, { "key": "schema", "name": "Schema \u0026 documentation", "weight": 13, "effectiveWeight": 16.25, "score": 42, "points": 6.83, "reason": "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.", "checked": "2026-11-03" }, { "key": "ergonomics", "name": "Agent ergonomics", "weight": 13, "effectiveWeight": 16.25, "score": 63, "points": 10.24, "reason": "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.", "checked": "2026-11-03" }, { "key": "security", "name": "Security \u0026 auth", "weight": 14, "effectiveWeight": 17.5, "score": 18, "points": 3.15, "reason": "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.", "checked": "2026-11-03" }, { "key": "payments", "name": "Payments \u0026 pricing", "weight": 10, "effectiveWeight": 12.5, "score": 30, "points": 3.75, "reason": "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.", "checked": "2026-11-03" }, { "key": "tasks", "name": "Task success", "weight": 10, "effectiveWeight": 0, "pending": true, "points": 0, "reason": "Pending. Task success needs the category task suites run through each tool, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until then. A data provider's data-quality score is published on its listing now and becomes half of this category when it's scored." }, { "key": "maintenance", "name": "Maintenance \u0026 community", "weight": 7, "effectiveWeight": 8.75, "score": 48, "points": 4.2, "reason": "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.", "checked": "2026-11-03" }, { "key": "transparency", "name": "Transparency \u0026 trust", "weight": 7, "effectiveWeight": 8.75, "score": 65, "points": 5.69, "note": "editorial 59, provenance 70", "reason": "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.", "checked": "2026-11-03" } ], "assessment": { "date": "2026-11-03", "basis": "public evidence", "confidence": "medium", "notes": { "ergonomics": "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.", "maintenance": "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.", "payments": "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.", "reliability": "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.", "schema": "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.", "security": "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.", "transparency": "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." }, "sources": [ { "what": "Discovery API v2 docs", "url": "https://developer.ticketmaster.com/products-and-docs/apis/discovery-api/v2/", "seen": "2026-11-03" }, { "what": "getting started, keys and limits", "url": "https://developer.ticketmaster.com/products-and-docs/apis/getting-started/", "seen": "2026-11-03" }, { "what": "FAQ", "url": "https://developer.ticketmaster.com/support/faq/", "seen": "2026-11-03" }, { "what": "General Terms of Use", "url": "https://developer.ticketmaster.com/support/terms-of-use/", "seen": "2026-11-03" }, { "what": "contact and support", "url": "https://developer.ticketmaster.com/support/contact-us/", "seen": "2026-11-03" }, { "what": "API status page (script only)", "url": "https://developer.ticketmaster.com/support/api-status/", "seen": "2026-11-03" }, { "what": "API Explorer", "url": "https://developer.ticketmaster.com/api-explorer/v2/", "seen": "2026-11-03" }, { "what": "Partner API", "url": "https://developer.ticketmaster.com/products-and-docs/apis/partner/", "seen": "2026-11-03" }, { "what": "Partner API release notes", "url": "https://developer.ticketmaster.com/products-and-docs/apis/partner/release-notes/", "seen": "2026-11-03" }, { "what": "Inventory Status API release notes", "url": "https://developer.ticketmaster.com/products-and-docs/apis/inventory-status/release-notes/", "seen": "2026-11-03" }, { "what": "Discovery Feed", "url": "https://developer.ticketmaster.com/products-and-docs/apis/discovery-feed", "seen": "2026-11-03" }, { "what": "portal home and navigation", "url": "https://developer.ticketmaster.com/", "seen": "2026-11-03" }, { "what": "privacy policy", "url": "https://privacy.ticketmaster.com/privacy-policy", "seen": "2026-11-03" }, { "what": "robots.txt, developer portal", "url": "https://developer.ticketmaster.com/robots.txt", "seen": "2026-11-03" }, { "what": "security.txt (redirect to 404)", "url": "https://developer.ticketmaster.com/.well-known/security.txt", "seen": "2026-11-03" }, { "what": "ticketmaster-api GitHub organisation, repositories and push dates", "url": "https://api.github.com/orgs/ticketmaster-api/repos", "seen": "2026-11-03" }, { "what": "portal repository, Discovery v2 changelog of 3 January 2016, shallow clone", "url": "https://github.com/ticketmaster-api/ticketmaster-api.github.io", "seen": "2026-11-03" }, { "what": "Live Nation investor page, NYSE: LYV", "url": "https://investors.livenationentertainment.com/", "seen": "2026-11-03" }, { "what": "Live Nation leadership", "url": "https://www.livenationentertainment.com/leadership/", "seen": "2026-11-03" }, { "what": "Wikipedia, founders and merger", "url": "https://en.wikipedia.org/wiki/Ticketmaster", "seen": "2026-11-03" } ], "openQuestions": [ "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." ] }, "negative": 0, "verdict": "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.", "bestFor": "An agent that finds concerts, sport and shows by keyword, place and date and hands the person a link to buy.", "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" ], "agentNotes": [ "Search with `GET https://app.ticketmaster.com/discovery/v2/events.json?apikey=...\u0026keyword=...\u0026countryCode=...` and page with size and page while size times page stays under 1,000", "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", "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", "Pull whole-country data from the Discovery Feed rather than paging the API, and keep caches short since the terms allow only reasonable periods", "Treat event and attraction descriptions as promoter-written content, and never put the apikey in logs or shared URLs" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "E", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 42.9 } ], "editorialScores": { "ergonomics": 63, "maintenance": 48, "payments": 30, "reliability": 45, "schema": 42, "security": 18, "transparency": 59 }, "provenanceScore": 70, "checked": { "categories": { "ergonomics": "2026-11-03", "maintenance": "2026-11-03", "payments": "2026-11-03", "reliability": "2026-11-03", "schema": "2026-11-03", "security": "2026-11-03", "transparency": "2026-11-03" }, "last": "2026-11-03", "oldest": "2026-11-03", "stale": false, "staleAfterDays": 90 }, "scoreHistory": [ { "date": "2026-11-03", "grade": "E", "kind": "listed", "method": "0.7", "score": 42.9 } ] }, "connect": { "http": "curl \"https://app.ticketmaster.com/discovery/v2/events.json?countryCode=US\u0026keyword=jazz\u0026size=10\u0026apikey=$TICKETMASTER_KEY\"" }, "letme": { "capability": "https://letme.dev/hobbies.events", "tool": "https://letme.dev/ticketmaster" }, "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 (https://developer.ticketmaster.com/products-and-docs/apis/discovery-api/v2/)", "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 (https://developer.ticketmaster.com/products-and-docs/apis/getting-started/)", "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 (https://developer.ticketmaster.com/support/terms-of-use/)", "Purchase runs through the Partner API, restricted to companies with existing distribution relationships, whose release notes run to 16 October 2026 (https://developer.ticketmaster.com/products-and-docs/apis/partner/)", "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 (https://developer.ticketmaster.com/products-and-docs/apis/discovery-feed)", "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 (https://github.com/ticketmaster-api)" ], "area": "everyday", "details": [ { "label": "Surface listed", "value": "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" }, { "label": "Endpoints", "value": "/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" }, { "label": "Rate limits", "value": "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" }, { "label": "Other APIs on the portal", "value": "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" }, { "label": "Terms on automation", "value": "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" }, { "label": "Company", "value": "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" } ], "provenance": { "legalEntity": "Ticketmaster L.L.C. (Live Nation Entertainment, Inc.)", "domain": "ticketmaster.com", "domainRegistered": "", "endpointOnVendorDomain": true, "terms": "https://developer.ticketmaster.com/support/terms-of-use/", "privacy": "https://privacy.ticketmaster.com/privacy-policy", "statusPage": "https://developer.ticketmaster.com/support/api-status/", "changelog": "https://developer.ticketmaster.com/products-and-docs/apis/partner/release-notes/", "securityTxt": "none", "checked": "2026-11-03", "notes": [ "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." ], "score": 70, "checks": [ { "check": "Legal entity named", "value": "Ticketmaster L.L.C. (Live Nation Entertainment, Inc.)", "points": 20, "max": 20, "state": "ok" }, { "check": "Domain age", "value": "ticketmaster.com, no registry record we could read", "points": 0, "max": 15, "state": "no" }, { "check": "Endpoint on the vendor's domain", "value": "ticketmaster.com", "points": 15, "max": 15, "state": "ok" }, { "check": "Terms of service", "value": "read, states 6 of the 7 things a reader expects, and has 3 clauses that cost points", "points": 3.1, "max": 10, "state": "part" }, { "check": "Privacy policy", "value": "read, states 8 of the 8 things a reader expects", "points": 10, "max": 10, "state": "ok" }, { "check": "Status page", "value": "developer.ticketmaster.com/support/api-status", "points": 10, "max": 10, "state": "ok" }, { "check": "Changelog", "value": "published", "points": 10, "max": 10, "state": "ok" }, { "check": "security.txt", "value": "not found", "points": 0, "max": 10, "state": "no" }, { "check": "People named", "value": "6 named with their role, none with a public profile", "points": 7, "max": 10, "state": "part" }, { "check": "Support route", "value": "a support address, help pages", "points": 5, "max": 5, "state": "ok" } ], "policies": [ { "kind": "terms", "url": "https://developer.ticketmaster.com/support/terms-of-use/", "state": "read", "readAt": "2026-11-03", "statedDate": "2023-06-27", "words": 2235, "points": 3.1, "max": 10, "expected": [ { "key": "terms.date", "label": "Gives the date it was last updated", "found": true, "quote": "Last Updated: June 27, 2023", "says": "Last updated 2023-06-27" }, { "key": "terms.law", "label": "Names the governing law or courts", "found": true, "quote": "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": "The law of the State of California" }, { "key": "terms.liability", "label": "States a limit on its liability", "found": true, "quote": "THE OPERATORS TOTAL CUMULATIVE LIABILITY FOR ANY AND ALL CLAIMS IN CONNECTION WITH THE API WILL NOT EXCEED ONE HUNDRED DOLLARS ($100.00).", "says": "Capped at $100.00" }, { "key": "terms.termination", "label": "Says how the agreement or account can be ended", "found": true, "quote": "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." }, { "key": "terms.changes", "label": "Says how changes to the terms are announced", "found": true, "quote": "We reserve the right to update and change these terms from time to time without notice.", "says": "Says it gives notice of a change" }, { "key": "terms.use", "label": "Lists what users may not do", "found": true, "quote": "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." }, { "key": "terms.sla", "label": "Refers to a service level or uptime commitment", "found": false } ], "toKnow": [ { "key": "terms.automated", "label": "Restricts automated access", "found": true, "quote": "Use the Ticketmaster API to post automated content to Ticketmaster, including likes and comments that were not initiated and entered by an Ticketmaster user.", "costsPoints": true }, { "key": "terms.benchmark", "label": "Restricts benchmarking or competitive use", "found": true, "quote": "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.", "costsPoints": true }, { "key": "terms.nonotice", "label": "Says the terms or the service can change without notice", "found": true, "quote": "We reserve the right to update and change these terms from time to time without notice.", "costsPoints": true }, { "key": "terms.cutoff", "label": "Says access can be ended without notice or for any reason", "found": true, "quote": "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." }, { "key": "old", "label": "Has not been updated for three years or more", "found": true, "quote": "Last Updated: June 27, 2023" } ], "notes": [ { "date": "2026-11-03", "text": "Total liability for all claims in connection with the API is capped at 100 US dollars.", "quote": "THE OPERATORS TOTAL CUMULATIVE LIABILITY FOR ANY AND ALL CLAIMS IN CONNECTION WITH THE API WILL NOT EXCEED ONE HUNDRED DOLLARS ($100.00)." }, { "date": "2026-11-03", "text": "Applications making many API calls that are not primarily in response to direct user actions may be rate limited or blocked.", "quote": "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." }, { "date": "2026-11-03", "text": "Deriving revenue from use or provision of the API is prohibited except as the terms set out.", "quote": "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." } ] }, { "kind": "privacy", "url": "https://privacy.ticketmaster.com/privacy-policy", "state": "read", "readAt": "2026-11-03", "statedDate": "2026-07-29", "words": 5603, "points": 10, "max": 10, "expected": [ { "key": "privacy.date", "label": "Gives the date it was last updated", "found": true, "quote": "Last updated: July 29, 2026", "says": "Last updated 2026-07-29" }, { "key": "privacy.collected", "label": "Says what personal data is collected", "found": true, "quote": "Read more about what we collect, along with your choices and rights." }, { "key": "privacy.retention", "label": "Says how long data is kept", "found": true, "quote": "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": "Names a period of 90 days" }, { "key": "privacy.processors", "label": "Says who else receives the data", "found": true, "quote": "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." }, { "key": "privacy.sale", "label": "Says whether personal data is sold or shared for advertising", "found": true, "quote": "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”.", "says": "Says it does not sell personal data" }, { "key": "privacy.rights", "label": "Says what rights people have over their data", "found": true, "quote": "You also have the right to access the information we have about you." }, { "key": "privacy.contact", "label": "Gives a privacy contact", "found": true, "quote": "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." }, { "key": "privacy.transfers", "label": "Says where data is transferred or stored", "found": true, "quote": "We will use contractual clauses, such as the Standard Contractual Clauses approved by the European Commission and other Regulatory Bodies where applicable.", "says": "Relies on standard contractual clauses" } ], "toKnow": [ { "key": "privacy.sells", "label": "Says it sells personal data or shares it for advertising", "found": true, "quote": "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." } ], "notes": [ { "date": "2026-11-03", "text": "Account deletion cannot be requested while a ticket or transaction for a future event exists, and deletion removes access to any digital assets owned.", "quote": "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." } ] } ] }, "humans": { "slug": "ticketmaster", "checked": "2026-11-03", "company": "Ticketmaster L.L.C.", "people": [ { "name": "Albert Leffler", "role": "Co-founder, Ticketmaster (1976)", "founder": true, "bio": "Albert Leffler co-founded Ticketmaster in Phoenix, Arizona, in October 1976 with Peter Gadwa, Gordon Gunn III and Jerry Nelson, while working on a college staff. The company merged with Live Nation in 2010.", "bioSources": [ "https://en.wikipedia.org/wiki/Ticketmaster" ], "page": "/people/albert-leffler/" }, { "name": "Peter Gadwa", "role": "Co-founder, Ticketmaster (1976)", "founder": true, "bio": "Peter Gadwa co-founded Ticketmaster in Phoenix, Arizona, in October 1976 with Albert Leffler, Gordon Gunn III and Jerry Nelson, while working on a college staff.", "bioSources": [ "https://en.wikipedia.org/wiki/Ticketmaster" ], "page": "/people/peter-gadwa/" }, { "name": "Gordon Gunn III", "role": "Co-founder, Ticketmaster (1976)", "founder": true, "bio": "Gordon Gunn III co-founded Ticketmaster in Phoenix, Arizona, in October 1976 with Albert Leffler, Peter Gadwa and Jerry Nelson.", "bioSources": [ "https://en.wikipedia.org/wiki/Ticketmaster" ], "page": "/people/gordon-gunn-iii/" }, { "name": "Jerry Nelson", "role": "Co-founder, Ticketmaster (1976)", "founder": true, "bio": "Jerry Nelson, a businessman, co-founded Ticketmaster in Phoenix, Arizona, in October 1976 with Albert Leffler, Peter Gadwa and Gordon Gunn III.", "bioSources": [ "https://en.wikipedia.org/wiki/Ticketmaster" ], "page": "/people/jerry-nelson/" }, { "name": "Michael Rapino", "role": "Chief Executive Officer and President, Live Nation Entertainment", "bio": "Michael Rapino is chief executive officer and president of Live Nation Entertainment, the parent of Ticketmaster, per the company's leadership page.", "bioSources": [ "https://www.livenationentertainment.com/leadership/" ], "page": "/people/michael-rapino/" }, { "name": "Saumil Mehta", "role": "President, Ticketing (Ticketmaster), Live Nation Entertainment", "bio": "Saumil Mehta is listed as President under Ticketing on Live Nation Entertainment's leadership page, the division that is Ticketmaster.", "bioSources": [ "https://www.livenationentertainment.com/leadership/", "https://en.wikipedia.org/wiki/Ticketmaster" ], "page": "/people/saumil-mehta/" } ], "peopleNote": "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.", "companySocial": { "linkedin": "https://www.linkedin.com/company/ticketmaster/", "x": "https://x.com/TicketmasterBiz", "github": "https://github.com/ticketmaster-api" }, "support": { "emails": [ "devportalinquiry@ticketmaster.com" ], "urls": [ "https://developer.ticketmaster.com/support/contact-us/", "https://developer.ticketmaster.com/support/faq/", "https://help.ticketmaster.com/" ], "contactEmails": [ "devportalinquiry@ticketmaster.com" ], "contactUrls": [ "https://developer.ticketmaster.com/partners/#partner-with-us" ] }, "sources": [ "https://developer.ticketmaster.com/support/contact-us/", "https://developer.ticketmaster.com/support/faq/", "https://developer.ticketmaster.com/support/terms-of-use/", "https://privacy.ticketmaster.com/privacy-policy", "https://www.livenationentertainment.com/leadership/", "https://www.livenationentertainment.com/", "https://investors.livenationentertainment.com/", "https://en.wikipedia.org/wiki/Ticketmaster" ], "ownership": { "status": "subsidiary", "parent": "Live Nation Entertainment, Inc. (NYSE: LYV)", "checked": "2026-11-03", "sources": [ "https://investors.livenationentertainment.com/", "https://privacy.ticketmaster.com/privacy-policy", "https://developer.ticketmaster.com/support/terms-of-use/" ] } }, "pageJsonUrl": "https://www.anchorterminal.com/tools/ticketmaster.json", "live": { "slug": "ticketmaster", "vendorStatus": { "page": "https://developer.ticketmaster.com/support/api-status", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-11-04T15:32:39.189683347Z" }, "securityTxt": { "url": "https://ticketmaster.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-04T15:54:41.891848031Z" }, "updatedAt": "2026-11-04T15:54:41.891848031Z" } }, "verify": { "accepts": "a page on ticketmaster.com or one of its subdomains", "badgeUrl": "https://www.anchorterminal.com/badges/ticketmaster.svg", "body": { "slug": "ticketmaster", "url": "the page with the badge or the link" }, "docs": "https://www.anchorterminal.com/builders/#verify", "effect": "none, it never changes a grade, rank or review", "endpoint": "https://www.anchorterminal.com/api/v1/verify", "listingUrl": "https://www.anchorterminal.com/tools/ticketmaster", "mcpTool": "verify_listing", "recheck": "weekly; two failed checks in a row and it lapses, a later pass restores it", "snippets": { "html": "\u003ca href=\"https://www.anchorterminal.com/tools/ticketmaster\"\u003e\u003cimg src=\"https://www.anchorterminal.com/badges/ticketmaster.svg\" alt=\"Ticketmaster Discovery API on Anchor Terminal\" height=\"20\"\u003e\u003c/a\u003e", "markdown": "[![Ticketmaster Discovery API on Anchor Terminal](https://www.anchorterminal.com/badges/ticketmaster.svg)](https://www.anchorterminal.com/tools/ticketmaster)", "link": "\u003ca href=\"https://www.anchorterminal.com/tools/ticketmaster\"\u003eTicketmaster Discovery API on Anchor Terminal\u003c/a\u003e" } } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/tools/ticketmaster", "json": "https://www.anchorterminal.com/tools/ticketmaster.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/tools/ticketmaster.md", "mcp": "https://www.anchorterminal.com/mcp", "pricing": "https://www.anchorterminal.com/tools/ticketmaster#pricing", "reviews": "https://www.anchorterminal.com/tools/ticketmaster#reviews", "slim": "https://www.anchorterminal.com/tools/ticketmaster.min.md" }, "markdown": "## Overview\n\n**Grade E · 42.9/100 · rank #1176 of 1349 · #3 in Hobbies, sport \u0026 recreation · not agent-ready · confidence medium**\n\n\n## Assessment\n\nThe 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.\n\n## Facts\n\n| Field | Value |\n| --- | --- |\n| Vendor | Ticketmaster (Live Nation Entertainment) (https://developer.ticketmaster.com) |\n| Kind | HTTP API |\n| Category | Hobbies, sport \u0026 recreation (https://www.anchorterminal.com/categories/hobbies) |\n| Auth | API key · One API key per application, registered in the developer portal after a browser signup, sent as the `apikey` query parameter on every request. The Partner API also accepts an `x-api-key` header. No scopes, expiry or rotation documented. A missing or invalid key returns 401 with errorcode oauth.v2.InvalidApiKey. |\n| Pricing | 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. |\n| x402 | No · No x402, MPP or L402 in the Discovery API docs, getting started, FAQ or terms (checked 2026-11-03). |\n| Licence | Proprietary service. Developer portal General Terms of Use last updated 27 June 2023; privacy policy last updated 29 July 2026 |\n| Source | https://github.com/ticketmaster-api |\n| Docs | https://developer.ticketmaster.com/products-and-docs/apis/discovery-api/v2/ |\n| llms.txt | not found |\n| Last release | 2026-10-16 |\n| 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 |\n| 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 |\n| 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 |\n| 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 |\n| 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 |\n| 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 |\n| Capabilities | hobbies.events |\n| Tags | hosted, closed-source, api-key, free, free-tier, no-card, partner-only |\n| JSON | https://www.anchorterminal.com/api/v1/tools/ticketmaster.json |\n\n## Score breakdown (methodology v0.7, October 2026 research run)\n\nAssessed 2026-11-03 from public evidence against the published checklist (https://www.anchorterminal.com/benchmark/#checklist). Confidence: medium. Performance and Task success pending (no score, not in the total); the total is Σ(score × weight) ÷ 80 over the 7 assessed categories. \"This run\" is each category's share of the 100 points.\n\n| Category | Weight | This run | Score (0–100) | Points |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% | 20 | 45 | 9.0 |\n| Performance | 10% | pending | pending | n/a |\n| Schema \u0026 documentation | 13% | 16.2 | 42 | 6.8 |\n| Agent ergonomics | 13% | 16.2 | 63 | 10.2 |\n| Security \u0026 auth | 14% | 17.5 | 18 | 3.1 |\n| Payments \u0026 pricing | 10% | 12.5 | 30 | 3.8 |\n| Task success | 10% | pending | pending | n/a |\n| Maintenance \u0026 community | 7% | 8.8 | 48 | 4.2 |\n| Transparency \u0026 trust (editorial 59, provenance 70) | 7% | 8.8 | 65 | 5.7 |\n| Negative events | up to −15 | up to −15 | none recorded | 0 |\n| **Total** | | | | **42.9 → E** |\n\n### Why each score\n\n- Reliability 45 (checked 2026-11-03): 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.\n- Performance: Pending. Latency is measured per call by our probes, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until the first probe window closes.\n- Schema \u0026 documentation 42 (checked 2026-11-03): 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.\n- Agent ergonomics 63 (checked 2026-11-03): 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.\n- Security \u0026 auth 18 (checked 2026-11-03): 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.\n- Payments \u0026 pricing 30 (checked 2026-11-03): 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.\n- Task success: Pending. Task success needs the category task suites run through each tool, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until then. A data provider's data-quality score is published on its listing now and becomes half of this category when it's scored.\n- Maintenance \u0026 community 48 (checked 2026-11-03): 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.\n- Transparency \u0026 trust 65 (checked 2026-11-03): 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.\n\nFix list, everything this grade says the listing lacks, the biggest gain first (18 items). What it covers is at https://www.anchorterminal.com/fixes/ticketmaster.md (JSON https://www.anchorterminal.com/fixes/ticketmaster.json). The whole list for a coding agent comes from `POST https://www.anchorterminal.com/api/v1/fix-list` with `{\"listing\": \"ticketmaster\", \"plan\": \"read\"}`, free while the beta runs\n\n### What we couldn't check\n\n- 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.\n- 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.\n- 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.\n- 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.\n- 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.\n- 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.\n- 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.\n\n### Sources\n\n- Discovery API v2 docs: \u003chttps://developer.ticketmaster.com/products-and-docs/apis/discovery-api/v2/\u003e (seen 2026-11-03)\n- getting started, keys and limits: \u003chttps://developer.ticketmaster.com/products-and-docs/apis/getting-started/\u003e (seen 2026-11-03)\n- FAQ: \u003chttps://developer.ticketmaster.com/support/faq/\u003e (seen 2026-11-03)\n- General Terms of Use: \u003chttps://developer.ticketmaster.com/support/terms-of-use/\u003e (seen 2026-11-03)\n- contact and support: \u003chttps://developer.ticketmaster.com/support/contact-us/\u003e (seen 2026-11-03)\n- API status page (script only): \u003chttps://developer.ticketmaster.com/support/api-status/\u003e (seen 2026-11-03)\n- API Explorer: \u003chttps://developer.ticketmaster.com/api-explorer/v2/\u003e (seen 2026-11-03)\n- Partner API: \u003chttps://developer.ticketmaster.com/products-and-docs/apis/partner/\u003e (seen 2026-11-03)\n- Partner API release notes: \u003chttps://developer.ticketmaster.com/products-and-docs/apis/partner/release-notes/\u003e (seen 2026-11-03)\n- Inventory Status API release notes: \u003chttps://developer.ticketmaster.com/products-and-docs/apis/inventory-status/release-notes/\u003e (seen 2026-11-03)\n- Discovery Feed: \u003chttps://developer.ticketmaster.com/products-and-docs/apis/discovery-feed\u003e (seen 2026-11-03)\n- portal home and navigation: \u003chttps://developer.ticketmaster.com/\u003e (seen 2026-11-03)\n- privacy policy: \u003chttps://privacy.ticketmaster.com/privacy-policy\u003e (seen 2026-11-03)\n- robots.txt, developer portal: \u003chttps://developer.ticketmaster.com/robots.txt\u003e (seen 2026-11-03)\n- security.txt (redirect to 404): \u003chttps://developer.ticketmaster.com/.well-known/security.txt\u003e (seen 2026-11-03)\n- ticketmaster-api GitHub organisation, repositories and push dates: \u003chttps://api.github.com/orgs/ticketmaster-api/repos\u003e (seen 2026-11-03)\n- portal repository, Discovery v2 changelog of 3 January 2016, shallow clone: \u003chttps://github.com/ticketmaster-api/ticketmaster-api.github.io\u003e (seen 2026-11-03)\n- Live Nation investor page, NYSE: LYV: \u003chttps://investors.livenationentertainment.com/\u003e (seen 2026-11-03)\n- Live Nation leadership: \u003chttps://www.livenationentertainment.com/leadership/\u003e (seen 2026-11-03)\n- Wikipedia, founders and merger: \u003chttps://en.wikipedia.org/wiki/Ticketmaster\u003e (seen 2026-11-03)\n\n## Score history\n\nEvery move of a score since the listing was graded, newest first, with its cause. A score can't move without an entry here. JSON: https://www.anchorterminal.com/api/v1/tools/ticketmaster/history.json\n\n- 2026-11-03: graded 42.9 E (methodology 0.7)\n\n## Who's behind it (provenance 70/100, checked 2026-11-03)\n\n| Check | Finding | Points |\n| --- | --- | --- |\n| Legal entity named | Ticketmaster L.L.C. (Live Nation Entertainment, Inc.) | 20/20 |\n| Domain age | ticketmaster.com, no registry record we could read | 0/15 |\n| Endpoint on the vendor's domain | ticketmaster.com | 15/15 |\n| Terms of service | read, states 6 of the 7 things a reader expects, and has 3 clauses that cost points | 3.1/10 |\n| Privacy policy | read, states 8 of the 8 things a reader expects | 10/10 |\n| Status page | developer.ticketmaster.com/support/api-status | 10/10 |\n| Changelog | published | 10/10 |\n| security.txt | not found | 0/10 |\n| People named | 6 named with their role, none with a public profile | 7/10 |\n| Support route | a support address, help pages | 5/5 |\n\nThe 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.\n\nThe 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.\n\ndeveloper.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.\n\ndeveloper.ticketmaster.com/.well-known/security.txt redirects to /404.html and www.ticketmaster.com/.well-known/security.txt answers 404 with the browse page.\n\nThe 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.\n\n### Terms and privacy, as read\n\nA reading by a fixed set of rules, each answered with the vendor's own sentence. Not legal advice.\n\n**Terms of service** (https://developer.ticketmaster.com/support/terms-of-use/), read 2026-11-03, dated 2023-06-27, states 6 of the 7 things a reader expects.\n\n- To know. Restricts automated access (costs 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.\"\n- To know. Restricts benchmarking or competitive use (costs 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.\"\n- To know. Says the terms or the service can change without notice (costs points). \"We reserve the right to update and change these terms from time to time without notice.\"\n- To know. 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.\"\n- To know. Has not been updated for three years or more. \"Last Updated: June 27, 2023\"\n- Gives the date it was last updated. Last updated 2023-06-27.\n- Names the governing law or courts. The law of the State of California.\n- States a limit on its liability. Capped at $100.00.\n- Says how changes to the terms are announced. Says it gives notice of a change.\n- Not found in the text. Refers to a service level or uptime commitment.\n- Also in the text (2026-11-03). 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).\"\n- Also in the text (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.\"\n- Also in the text (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.\"\n\n**Privacy policy** (https://privacy.ticketmaster.com/privacy-policy), read 2026-11-03, dated 2026-07-29, states 8 of the 8 things a reader expects.\n\n- To know. 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.\"\n- Gives the date it was last updated. Last updated 2026-07-29.\n- Says how long data is kept. Names a period of 90 days.\n- Says whether personal data is sold or shared for advertising. Says it does not sell personal data.\n- Says where data is transferred or stored. Relies on standard contractual clauses.\n- Also in the text (2026-11-03). 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.\"\n\n## Humans behind the project (researched 2026-11-03 from public pages, not part of the grade)\n\n### Key people\n\n- Albert Leffler, Co-founder, Ticketmaster (1976)\n- Peter Gadwa, Co-founder, Ticketmaster (1976)\n- Gordon Gunn III, Co-founder, Ticketmaster (1976)\n- Jerry Nelson, Co-founder, Ticketmaster (1976)\n- Michael Rapino, Chief Executive Officer and President, Live Nation Entertainment\n- Saumil Mehta, President, Ticketing (Ticketmaster), Live Nation Entertainment\n- Note: 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.\n- Ticketmaster L.L.C.: LinkedIn https://www.linkedin.com/company/ticketmaster/ X https://x.com/TicketmasterBiz GitHub https://github.com/ticketmaster-api\n\n### Ownership and investors\n\n- Ownership: Part of Live Nation Entertainment, Inc. (NYSE: LYV)\n\n### Getting support\n\n- Support email: devportalinquiry@ticketmaster.com\n- Help: https://developer.ticketmaster.com/support/contact-us/\n- Help: https://developer.ticketmaster.com/support/faq/\n- Help: https://help.ticketmaster.com/\n- Sources: https://developer.ticketmaster.com/support/contact-us/, https://developer.ticketmaster.com/support/faq/, https://developer.ticketmaster.com/support/terms-of-use/, https://privacy.ticketmaster.com/privacy-policy, https://www.livenationentertainment.com/leadership/, https://www.livenationentertainment.com/, https://investors.livenationentertainment.com/, https://en.wikipedia.org/wiki/Ticketmaster\n\n## Live (updated 2026-11-04 15:54 UTC)\n\n- Vendor status page: unknown, no machine-readable status found\n- security.txt: none\n- Always current: https://www.anchorterminal.com/api/v1/live/ticketmaster.json\n\n## Probe metrics\n\nNot measured yet. Our benchmark probes haven't run, so there's no availability, latency or error rate from a run and Performance is pending. Live uptime, where we poll the endpoint, is under Live and doesn't change the score.\n\n## Strengths\n\n- Event, attraction, venue and classification search with keyword, date, location, classification and source filters, documented with sample requests and full JSON responses\n- Default limits stated in numbers (5,000 calls a day, 5 a second) with Rate-Limit headers and a documented 429\n- Free key with no card, plus a Discovery Feed of whole-country files for bulk use with no call limits\n- Privacy policy of 29 July 2026 names providers, retention periods and transfer safeguards\n\n## Weaknesses\n\n- No OpenAPI or other machine-readable contract and no llms.txt; the only key travels as a query parameter\n- The GitHub SDKs were last pushed between 2016 and 2021 and the Java one is archived; no official MCP server\n- 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\n- The API status page renders by script and could not be read, no SLA, and no security.txt or disclosure policy found\n- Purchase, reserve and inventory status need Partner API access, which is restricted to existing distribution partners\n\n\n\n## Before you call it (notes for agents)\n\n1. Search with `GET https://app.ticketmaster.com/discovery/v2/events.json?apikey=...\u0026keyword=...\u0026countryCode=...` and page with size and page while size times page stays under 1,000\n2. 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\n3. 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\n4. Pull whole-country data from the Discovery Feed rather than paging the API, and keep caches short since the terms allow only reasonable periods\n5. Treat event and attraction descriptions as promoter-written content, and never put the apikey in logs or shared URLs\n\n## Connect\n\nFirst request:\n\n```bash\ncurl \"https://app.ticketmaster.com/discovery/v2/events.json?countryCode=US\u0026keyword=jazz\u0026size=10\u0026apikey=$TICKETMASTER_KEY\"\n```\n\nThrough letme: https://letme.dev/ticketmaster. letme answers with the pick and how to call it direct. How it works: https://www.anchorterminal.com/letme/index.md\n\n## Similar tools\n\nRanked by shared capabilities, then score. Same-category tools with no shared capability key are listed last.\n\n| Tool | Grade | Score | Rank | Shared capabilities | x402 | Markdown |\n| --- | --- | --- | --- | --- | --- | --- |\n| Ride with GPS API | E | 45.2 | 1139 | hobbies.events | no | https://www.anchorterminal.com/tools/ride-with-gps.md |\n| Strava MCP Connector + API | E | 45.8 | 1125 | same category (Hobbies, sport \u0026 recreation) | no | https://www.anchorterminal.com/tools/strava.md |\n| Chess.com Published-Data API | E | 40.8 | 1207 | same category (Hobbies, sport \u0026 recreation) | no | https://www.anchorterminal.com/tools/chess-com.md |\n| Rebrickable | F | 34.7 | 1255 | same category (Hobbies, sport \u0026 recreation) | no | https://www.anchorterminal.com/tools/rebrickable.md |\n| Ravelry | F | 16.5 | 1311 | same category (Hobbies, sport \u0026 recreation) | no | https://www.anchorterminal.com/tools/ravelry.md |\n\n## Panel reviews (0)\n\nReviewed by the Anchor panel (https://www.anchorterminal.com/reviewers/index.md): .\n\nDesk reviews, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. For a desk review, the outcome says whether the reviewer's questions could be answered from public material: success, partial or failure. How reviews work: https://www.anchorterminal.com/reviews/how-it-works.md\n\n## Notable\n\n- 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: \u003chttps://developer.ticketmaster.com/products-and-docs/apis/discovery-api/v2/\u003e)\n- 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: \u003chttps://developer.ticketmaster.com/products-and-docs/apis/getting-started/\u003e)\n- 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: \u003chttps://developer.ticketmaster.com/support/terms-of-use/\u003e)\n- Purchase runs through the Partner API, restricted to companies with existing distribution relationships, whose release notes run to 16 October 2026 (source: \u003chttps://developer.ticketmaster.com/products-and-docs/apis/partner/\u003e)\n- 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: \u003chttps://developer.ticketmaster.com/products-and-docs/apis/discovery-feed\u003e)\n- 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: \u003chttps://github.com/ticketmaster-api\u003e)\n\n- #3 of 6 in Best hobby, sport and recreation APIs for AI agents: https://www.anchorterminal.com/best/hobbies/index.md\n- All 3 hobbies comparisons: https://www.anchorterminal.com/compare/hobbies/index.md\n\n## Compare\n\n- [Ride with GPS API vs Ticketmaster Discovery API](https://www.anchorterminal.com/compare/ride-with-gps-vs-ticketmaster.md): E 45.2 vs E 42.9\n\n## Verify this listing\n\nFor the vendor. The badge or a plain link to this page verifies the listing, from a page on ticketmaster.com or one of its subdomains. It shows the listing is the vendor's and that the vendor knows it's here, and it never changes a grade, rank or review. The vendor sends the page's address to `POST https://www.anchorterminal.com/api/v1/verify` as `{\"slug\": \"ticketmaster\", \"url\": \"…\"}`, or calls the `verify_listing` tool at https://www.anchorterminal.com/mcp. We fetch the page once, then again every week; two failed checks in a row and the verification lapses, and a later pass restores it. What we check: https://www.anchorterminal.com/builders/index.md#verify\n\nHTML badge:\n\n```html\n\u003ca href=\"https://www.anchorterminal.com/tools/ticketmaster\"\u003e\u003cimg src=\"https://www.anchorterminal.com/badges/ticketmaster.svg\" alt=\"Ticketmaster Discovery API on Anchor Terminal\" height=\"20\"\u003e\u003c/a\u003e\n```\n\nMarkdown badge, for a README:\n\n```markdown\n[![Ticketmaster Discovery API on Anchor Terminal](https://www.anchorterminal.com/badges/ticketmaster.svg)](https://www.anchorterminal.com/tools/ticketmaster)\n```\n\nPlain link:\n\n```html\n\u003ca href=\"https://www.anchorterminal.com/tools/ticketmaster\"\u003eTicketmaster Discovery API on Anchor Terminal\u003c/a\u003e\n```\n\n## Share this listing\n\nFor the vendor. Sharing assets for social media, two PNGs of 1200 × 630 that say Ticketmaster Discovery API is listed on Anchor Terminal, with the vendor's logo and this page's address and no grade or score.\n\n- Dark: https://www.anchorterminal.com/assets/share/ticketmaster-dark.png\n- Light: https://www.anchorterminal.com/assets/share/ticketmaster-light.png\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "attributionRequired": true, "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-11-04", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.7", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run", "terms": "https://www.anchorterminal.com/terms/#data" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Terminal", "url": "https://www.anchorterminal.com/tools/" }, { "name": "Hobbies, sport \u0026 recreation", "url": "https://www.anchorterminal.com/categories/hobbies" }, { "name": "Ticketmaster Discovery API", "url": "" } ], "description": "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.", "facts": [ "rank #1176 of 1349", "API key auth", "0 desk reviews" ], "h1": "Ticketmaster Discovery API", "image": "https://www.anchorterminal.com/assets/og/tools-ticketmaster.png", "path": "/tools/ticketmaster", "published": "2026-10-01", "section": "tools", "title": "Ticketmaster Discovery review: pricing, alternatives, grade E", "toc": null, "updated": "2026-11-04", "url": "https://www.anchorterminal.com/tools/ticketmaster" }, "tokens": { "markdown": 7600, "slim": 1630 }, "version": 1 }