Ride with GPS API vs Ticketmaster Discovery API

Ride with GPS API 72

Public OpenAPI 3.0.1 file with 34 paths, 61 operations and 41 schemas (25). ridewithgps.com/llms.txt describes the product and plans but links no Markdown docs, and the documentation is HTML (5 of 10). Operation descriptions say which endpoints are organisation-only, that uploads and package builds return a task to poll, how experience codes replace each other and that deleting a member keeps their account; little on when not to use an operation (14 of 20). 18 enums, required fields and defaults in the file, but the Error schema is an array of strings (10 of 15). One example in the OpenAPI file, request and pagination examples on the docs pages, and a table of HTTP codes with the errors array shape (8 of 15). One version in the path, a rule that only incompatible changes create a new version, and a dated change log back to January 2025 (15). 25 + 5 + 14 + 10 + 8 + 15 = 72.

Ticketmaster Discovery API 42

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.

Ride with GPS API 24

Read with the hosted lines. No status page, since status.ridewithgps.com answers 301 to the home page and the docs link none (0). No readable incident history (5). The API terms of 11 September 2026 say no fixed request limits currently apply and ask for caching, webhooks and backing off, so there are no numbers to publish (5 of 15). No 429 is documented in the docs or the OpenAPI file; the terms ask clients to back off on failures, uploads run as tasks to poll, and no idempotency key exists for the 30 write operations (4 of 15). No SLA (0). v1 is the current and only version with no beta label (10). 0 + 5 + 5 + 4 + 0 + 10 = 24.

Ticketmaster Discovery API 45

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.

Ride with GPS API 30

OAuth 2.0 authorisation code flow with one scope, user, and a revoke endpoint, but no PKCE, expiry or refresh token is documented; basic auth tokens are minted from the account email and password with no documented expiry or revocation; credentials travel in headers (18 of 30). No read-only scope, and the 30 write operations, including deletes of routes, events, members and experiences, need no confirmation (4 of 20). Route names, descriptions, event text and experience messages are user content with no guidance on treating them as untrusted (5 of 15). The API clients page lists clients and tokens; no call log is documented (3 of 15). /.well-known/security.txt returns 404, and no disclosure policy, bug bounty or certification was found (0 of 20). 18 + 4 + 5 + 3 + 0 = 30.

Ticketmaster Discovery API 18

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.

Ride with GPS API 60

Read for a closed service. The newest change log entry is 14 October 2026 (30). Five dated entries since 4 August 2026, on 10 August, 3 September, 11 September, 6 October and 14 October (20). A dated change log, developers@ridewithgps.com and a Zendesk help centre that answered 403 to our reader; replies were not tested (10 of 15). No official SDK and no entry in the official MCP registry (0 of 15). No package or CI to judge (0 of 10). 30 + 20 + 10 + 0 + 0 = 60.

Ticketmaster Discovery API 48

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.

Ride with GPS API 57

No field selection; polylines and track files sit on separate endpoints and page_size runs from 20 to 200 (12 of 25). page and page_size with meta.pagination, filters for name, visibility, distance, elevation gain, archived and stationary, and privacy_code for non-public items (20). Errors carry HTTP codes and an errors array of messages with no codes to branch on (10 of 20). Reads are safe to repeat and package builds return 409 while one runs, but no idempotency key covers creates, and deletes are not confirmed (8 of 20). Two headers and a .json suffix are all a request needs, with no official SDK (7 of 15). 12 + 20 + 10 + 8 + 7 = 57.

Ticketmaster Discovery API 63

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.

Ride with GPS API 59

Closed service with API terms effective 11 September 2026 and general terms of 1 July 2026 naming Ride with GPS, Inc under Oregon law; the App Store names Ride with GPS LLC (15 of 30). The privacy policy of 31 July 2026 gives no fixed retention periods, names Google Maps, Google and Apple and other providers only by category, and names no entity (12 of 30). The API terms promise reasonable advance notice of material changes through the change log or email, and the 23 March 2026 breaking change to activity_types shipped with a migration map and no notice window (10 of 20). Processing in the United States and other jurisdictions with safeguards where required; no subprocessor list (6 of 20). 15 + 12 + 10 + 6 = 43.

Ticketmaster Discovery API 65

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.