> ## Documentation Index
> Fetch the complete documentation index at: https://docs.rewind.rest/llms.txt
> Use this file to discover all available pages before exploring further.

# Attending

> Live events, tickets, and game attendance parsed from your calendar and inbox, with sports score enrichment.

## 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](https://schema.org/EventReservation) schema parser as a fallback for everything else.

Events sync daily, with incremental Gmail and Calendar pulls. Browse every endpoint in the [API reference](/api-reference/attending/list-attended-events).

## Event categories

Every event has a top-level `category` 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 in `event_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](/api-reference/attending/get-attended-season) 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](/api-reference/attending/get-attended-event).

## Filtering

The events endpoint supports filtering by:

* `category`: `sports`, `music`, or `arts`.
* `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`: `1` for confirmed attendance, `0` for tickets bought but not used, omit for both.

## Year in review

The [year in review endpoint](/api-reference/attending/year-in-review) returns a monthly breakdown of your attended events for a given year, plus top venues and top performers.

## From Claude

You can also explore your attendance history from Claude. Set up the [MCP server](/mcp/overview), then the [attending tools](/reference/mcp-tools/attending) are yours. Ask which games you went to this season, or your team's attended record.