Total Parks API
Total Parks API
Programmatic access to public park facts, availability, carts, and bookings. Base URL: https://api.totalparks.com.au.
OpenAPI
Download the filtered public specification from https://totalparks.com.au/openapi.json. HTML companion: Total Parks OpenAPI specification. The same JSON is served at https://api.totalparks.com.au/docs/openapi.json. Interactive Swagger UI: https://api.totalparks.com.au/docs.
Versioning
The current totalparks REST surface is major version 1. Unversioned paths are v1. Send optional API-Version: 1 or omit the header. Breaking changes require a new major. Deprecations use RFC 9745 Deprecation and RFC 8594 Sunset headers. Full policy: Total Parks API versioning.
Authentication
Anonymous reads are available for public discovery endpoints advertised in the OpenAPI document. Guest checkout uses a bearer cart token. User and operator OAuth is described at Total Parks auth docs and OAuth authorization server metadata. Personal access tokens use the tp_pat_ prefix.
Carts and bookings
Human checkout remains on Total Parks. Carts are server-authoritative (POST /carts, prepare, Stripe, confirm). Agents should not treat cart create as a public anonymous MCP tool. Send travellers to Total Parks room-page booking URLs when a stay looks viable.
MCP
Park-specific questions, room or site detail, bounded availability calendars, and stay feasibility belong on the Total Parks MCP connector.
Webhooks
There is no public outbound webhook product for third-party developers. See Total Parks webhooks. PMS webhooks are an operator integration, not a partner event bus.