ThemeParks.wiki

API Pricing

Live wait times, opening hours and historical data for theme parks worldwide, over REST and websockets. Every limit below is read from the running API. New here? Start with the API documentation.

No key? Anonymous requests get 7 days of history and 60 history requests per hour.

History depth is per park: see what the archive holds for yours, going how far back, without a key.

Prices as published on 21 September 2026.

Enterprise

from $500/month

Talk to us about Enterprise

  • Websocket firehose (all entities); connection and subscription limits agreed in your contract
  • Full dataset + custom data sets
  • Redistribution negotiated case-by-case (named, revocable exception — not a standard right)
  • Dedicated support
  • 99.9% availability SLA (REST API and websockets)
  • Custom REST capacity, agreed in your contract
History: Full archive
REST: Negotiated capacity
History requests: Negotiated capacity
Websockets: 1,000 connections, firehose included
Support: Dedicated
SLA: 99.9% availability (REST API and websockets)
Licence: Custom

Live and historical data is provided best-effort and is known to be incomplete: it is whatever we captured live, so it has gaps from outages, parks not returning data, and parks not yet implemented. No accuracy or freshness guarantee. Availability SLA on Business and Enterprise. The SLA covers our REST API and websocket service responding, not the completeness, freshness or accuracy of park data, which comes from the parks. The two are measured as one figure: a minute is down if either is.

Questions

What's free?

Live wait times and schedules over REST, for everyone, commercial use included. A free key gets you 300 requests per minute, 30 days of history and 1 websocket connection. Without a key, 7 days of history.

What do the plans add?

Higher rate limits, more websocket connections and the firehose, and history further back: 400 days on Pro, full archive on Business.

How far back does the history actually go?

It varies by park, so we publish it: the data coverage page lists every park, how far back each one goes, and when it was last added to. No key needed.

Is the free tier changing?

No. For accounts that already exist, published free-tier limits only ever move up. That floor is in the terms.

What happens to my key if I do nothing?

Nothing. Same key, same limits, same history.

Can I build a product on this?

Yes, that is what it is for. A mobile app, watch app, website or dashboard that shows wait times to people is welcome, free or paid, ads or no ads, no permission needed. On the free tier, show a "Powered by ThemeParks.wiki" credit; paid plans drop that requirement.

The one thing you cannot do is pass the data on as data for other software to consume: running your own wait-times API, a public feed, widgets embedded on other people's sites, or letting your own users bulk-export ThemeParks.wiki data — live or historical — out of your product. Downloading it for your own use is fine, the whole archive your plan reaches included: that is what the paid plans are for. That holds on every self-serve plan; Enterprise can negotiate an exception in writing.

Can I cancel?

Any time, from your profile or through Paddle. You keep access to the end of the period you have paid for, and nothing further is charged.

Will the price go up?

Not while you stay subscribed. The price you sign up at is the price you keep. It covers the price, not what a plan includes.

Is there an uptime guarantee?

Business: 99.5% availability (REST API and websockets). Enterprise: 99.9% availability (REST API and websockets). Both are assessed per whole UTC calendar month on the figure published at status.themeparks.wiki, starting with October 2026 — a subscription bought before then is not assessed for the remainder of that month. They cover the REST API and the websocket service responding, measured as one figure — a minute is down if either is — and not the parks' data being complete or fresh. The free tier and Pro carry none.

If I stop

This is one person, and that is worth being honest about rather than leaving you to guess. The library that fetches the parks’ data is open source and MIT licensed (parksapi), so collecting this data does not depend on me existing.

If I ever could not run the service, my intention — best efforts, not a contract — is to give notice rather than disappear, to keep the free API running for as long as it is funded, and to find a home for the archive rather than let it go dark. If the service wound down while you were subscribed, the unused part of what you paid would come back to you.

If the project were ever sold, I would do everything in my power to make these commitments part of the deal, the free-tier floor and the price lock included, and my intention is to say so publicly rather than let you find out afterwards.

Billing and terms

Prices are in USD for every buyer. The checkout shows the total you will be charged, with VAT included where it applies. Payments are processed by Paddle, who act as the merchant of record.

Terms & acceptable use sets out what you may do with the data, and contains the refund policy. The privacy notice covers your data. The reliability page covers uptime.

Questions about a plan, or need something that is not listed? Write to hello@themeparks.wiki.