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

# Event vs. occurrence

> How Momentra groups recurring programming so counts don't inflate.

Momentra distinguishes the underlying thing from each of its dated instances.

* **Event** — the underlying thing (a run club, a theater production, a
  workshop).
* **Occurrence** — a specific dated/timed instance of that event.

A theater production with 15 performances is **1 event / 15 occurrences**, not 15
events. Recurring instances are grouped so recurring programming doesn't inflate
counts.

## Where the counts show up

A scrape response reports both totals in its `meta`:

```json theme={null}
{
  "meta": {
    "eventCount": 35,
    "occurrenceCount": 35
  }
}
```

## The schedule block

Each event carries a `schedule` describing whether it's a one-off, a series, or
recurring, with the occurrences nested under it:

```json theme={null}
{
  "schedule": {
    "type": "single",
    "startDate": "2026-09-19T09:30:00-04:00",
    "endDate": "2026-09-19T11:00:00-04:00",
    "occurrences": [
      {
        "startDate": "2026-09-19T09:30:00-04:00",
        "endDate": "2026-09-19T11:00:00-04:00",
        "duration": "PT1H30M",
        "eventStatus": "EventScheduled",
        "ticket_status": "on_sale",
        "seatsRemaining": null,
        "waitlistAvailable": false
      }
    ]
  }
}
```

`schedule.type` is one of `single`, `series`, or `recurring`.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.