Overview
The Attending domain tracks live events you bought tickets for: sports games, concerts, theater, and other one-off events. Events come from two sources:- Google Calendar: auto-extracts ticketing details from event descriptions when Google’s parsers populate them.
- Gmail: per-vendor parsers for the major ticket sellers, with a universal EventReservation schema parser as a fallback for everything else.
Event categories
Every event has a top-levelcategory and a more specific event_type:
| Category | Event types |
|---|---|
sports | mlb_game, nfl_game, nba_game, wnba_game, mls_game, ncaaf_game, ncaab_game |
music | concert |
arts | theater, comedy, other |
Sports enrichment
Sports events are enriched with team and score data: MLB from the MLB Stats API, and NFL, NBA, WNBA, MLS, NCAAF, and NCAAB from ESPN. Each event carries league-specific fields inevent_data, such as final scores, the winning pitcher, and my_team_won.
The full team object, with name, brand colors, and light and dark logo variants, is denormalized onto every event, player, and appearance, so you never need a second call to render a logo or tint. For MLB, box scores also resolve into per-player appearance lines on the players endpoints.
W/L on the seasons endpoint counts only games you attended (attended=1), so a 6-game home season with one no-show reports 5-1, not the team’s full 5-2. The exact event_data and team field shapes are in the API reference.
Filtering
The events endpoint supports filtering by:category:sports,music, orarts.event_type: specific event type (e.g.,mlb_game,concert).season/year: sports season or calendar year.venue_id: filter to a single venue.attended:1for confirmed attendance,0for tickets bought but not used, omit for both.