Docs

Public API docs for humans and agents.

The OpenAPI document is the contract, Scalar is the interactive reference, and these pages explain how to use the Austin-first API without guessing.

API referenceOpenAPI JSONAPI index

Events

Read city lists first, then request event detail only when needed.

List route

GET /api/v1/cities/{citySlug}/events

  • Supports `limit`, `page`, `interest`, `format`, `free_only`, `q`, `starts_after`, and `starts_before`.
  • Returns paginated event summaries with `nextOccurrence` and source attribution.
  • Prefer this route for discovery and refresh loops.
curl "https://gotplans.ai/api/v1/cities/austin/events?limit=10&interest=music&free_only=true"

Detail route

GET /api/v1/events/{eventId}

  • Returns full `occurrences`, top-level `sourceLinks`, and `longDescription` when available.
  • Use this after narrowing candidates from the city list route.
  • Do not poll event detail aggressively when list data is enough.
curl "https://gotplans.ai/api/v1/events/{eventId}"

Austin-first notes

  • Event freshness can change as recurring series are re-verified.
  • Source links and `primarySourceUrl` are part of the contract; use them.
  • Today the public event surface is Austin-first, even though other Texas cities are modeled in the index.