This site is a home for the theme park API knowledge I have collected over the years. It is meant to preserve practical details that are easy to lose: how services fit together, what payloads mean, which behaviors are surprising, and when something was last observed.
These are independent research notes. They are not official documentation and are not affiliated with any park operator.
What belongs here
- Service and endpoint overviews
- Authentication flows and session behavior
- Request and response examples with sensitive values removed
- Field definitions, units, and status mappings
- Known quirks, regional differences, and historical changes
- A clear last verified date wherever behavior may change
How the documentation is organized
Each park or operator gets its own section. Start with an overview page, then split larger subjects into focused pages such as authentication, destinations, attractions, schedules, or wait times.
The files live locally in the content folder. Every deployment bundles the current Markdown into the Worker, so no public Git repository or separate content service is required.
Accuracy and responsible use
Document observations carefully, distinguish confirmed behavior from inference, and never publish credentials, session tokens, personal data, or instructions intended to bypass access controls. API behavior can change without notice; record dates and app versions when they matter.