OpenTeeSheet open data format

Your venue's data is yours. Every venue, bay, booking, door grant and bay session on OpenTeeSheet has a published JSON Schema (draft 2020-12), the API returns those records, and one command exports all of them as a single document. Free on every plan, at any time, with no request to support and no fee. Anyone may implement the format.

Export everything in one command

From a terminal (the key is created on your account page, Agent access):

npx openteesheet login            # paste the key from Account -> Agent access
npx openteesheet export --out my-venue.json

Or straight from the API, or ask your AI agent to call the MCP tool export_venue_data. All three return the same document:

curl -H "Authorization: Bearer $OPENTEESHEET_API_KEY" \
  https://openteesheet.com/api/v1/venue/export > my-venue.json

{
  "format": "openteesheet.venue-export",
  "version": 1,
  "schema": "https://openteesheet.com/schemas/venue-export.schema.json",
  "exported_at": "2026-11-02T12:00:00.000Z",
  "venue": { "object": "venue", "id": "...", "name": "...", ... },
  "bays": [ { "object": "bay", ... } ],
  "bookings": [ { "object": "booking", ... } ],
  "door_grants": [ { "object": "door_grant", ... } ],
  "bay_sessions": [ { "object": "bay_session", ... } ],
  "counts": { "bays": 4, "bookings": 1250, "door_grants": 1190, "bay_sessions": 980 }
}

A door grant says which lock, which method, which window and whether it is live; the code itself is never exported. Times are UTC (RFC 3339) and the venue record carries its IANA time zone. Prices are in cents.

Golfers: your own sessions, every venue

A golfer's own session history at every OpenTeeSheet venue (venue, bay, launch monitor, how each session started, the bay's real start and stop where it reports them, minutes played, how it ended) downloads from the account page, or with npx openteesheet my-sessions --out my-sessions.json, GET /api/v1/me/sessions or the MCP tool export_my_sessions, as one document matching https://openteesheet.com/schemas/golfer-sessions.schema.json. Shot and round data is not in it: no launch-monitor maker shares shot data with OpenTeeSheet yet.

Schemas

Each object has its own file; the bundle /schema/openteesheet-v1.json holds all of them under $defs. Records never carry payment-processor ids or secrets.

Every job, three ways

The REST API is documented in /openapi.json (each operation declares its security: a bearer API key; read jobs take a read key, writes a write key). The MCP server is https://openteesheet.com/mcp and the CLI is npx openteesheet; setup for each is on Use with your AI agent. Destructive jobs (cancel, move a booking, re-issue a door code) answer what would happen first and act only on confirm. An owner can also move a booking to a new time or another bay through the API and the MCP tool reschedule_venue_booking; the price stays as booked and the golfer gets a new door code.

Stability

Version 1. Fields are added only as optional; a field is never renamed or removed within a version, and the export names its schema URL so a reader can always check what it got. The API's responses for these objects are validated against these exact files in our test suite, so a field cannot drift without a test failing.