v1

Daily summaries of an entity's history

Changed on

Returns one summary row per park-local day: minutes operating, down and unknown, first opening and last close, wait statistics, show count and change count. Parameters are as for /history; rows cover whole days. A call covers up to 3660 days and is never paged. Days with no data are left out. So are standby, singleRider and showCount when there was nothing of that kind.

A run lasts from a change to OPERATING until the next change to CLOSED or REFURBISHMENT, DOWN periods included. A row is counted like this:

  • Outside the park's published hours, an OPERATING status counts as unknownMinutes, not operatingMinutes, after 4 hours or more unconfirmed. On a day with published hours, only a status change confirms it; a status carried over midnight is unconfirmed. On other days, any change but showtimes confirms it, across midnight.
  • From 2026-10-08, also in published hours and for DOWN, after 24 hours absent from the park's feed (exceptions in the history notes).
  • A wait counts only while the entity is OPERATING and on the day it was posted. The wait showing when a ride opens counts if it last changed within 24 hours.
  • extremeWaits counts readings of 480 minutes or more. implausibleWaits counts readings above the destination's plausibility ceiling (600 minutes or lower, see the history notes), which are left out of the statistics; the rest stay in. Wait values above 1440 minutes (24 hours) are feed errors and are omitted.
  • firstOperatingAt is null when the entity did not change to OPERATING that day; it may still have operated, carried over from the day before.
  • lastClosedAt is when the last run that started that day closed, which can be after midnight. The next day's row does not repeat it.
  • inParkHours repeats the numbers for the park's published hours, when it published any.
  • A row without unknownMinutes was counted under earlier rules.

To rebuild a row from /history, use that day's and the next day's history, the park's schedule for both days, opening.observedAtByKind and opening.observedAt.

For a park, the 200 is HistoryParkDailyEnvelope, with an entities[] array in place of coverage and days. Park calls are paged, 31 park-local days at a time, with next for the rest. Every other entityType gets the single-entity shape, so the 200 is a union of two schemas selected by entityType. A call costs one unit of the hourly history budget, however large the park.

See "Limits" above for the history window and hourly budget.

get/v1/entity/{id}/history/daily

Request

  • Base URL
    https://api.themeparks.wiki
  • URL
    https://api.themeparks.wiki/v1/entity/{id}/history/daily
  • Auth
    • none
    • or API key in header X-API-Key

Path parameters

idstring required

The entity: its UUID, its slug, or for a destination its externalId.

Query parameters

datestring date

One park-local day, YYYY-MM-DD. Cannot be combined with from/to.

fromstring

Start: a park-local day (YYYY-MM-DD) or an RFC 3339 instant with an offset; rows are always whole days. from and to must be the same form.

tostring

End: a day (inclusive) or an instant (exclusive). Defaults to today. Up to 3660 park-local days per call.

Response

Successful response

OR

Changes

    • info

      added the optional property ////// to the response with the status

    • info

      added the optional property /////// to the response with the status

    • info

      added the optional property //////// to the response with the status

    • info

      added the optional property ///////// to the response with the status

    • breaking

      added to the response body oneOf list for the response status

    • breaking

      the response's body type changed from object to no type for status

    • breaking

      removed the required property from the response with the status

    • info

      added the optional property ////// to the response with the status

    • info

      added the optional property ////// to the response with the status

    • info

      added the optional property ////// to the response with the status

    • info

      added the optional property //////// to the response with the status

    • info

      added the optional property //////// to the response with the status

    • info

      added the optional property //////// to the response with the status