--- title: "Daily summaries of an entity's history" method: GET path: "/v1/entity/{id}/history/daily" tags: ["v1"] --- # Daily summaries of an entity's history `GET /v1/entity/{id}/history/daily` ## Request - Base URL: `https://api.themeparks.wiki` - URL: `https://api.themeparks.wiki/v1/entity/{id}/history/daily` - Auth: one of: - none - API key in header `X-API-Key` 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. ## Path parameters - `id` string, required ## Query parameters - `date` string, date - `from` string - `to` string ## Response `200` Successful response - union - HistoryDailyEnvelope: One entity's daily summary. For a PARK the same call returns HistoryParkDailyEnvelope. range is always whole park-local days (YYYY-MM-DD), and today's row is the day so far. - `id` string, required - `name` string, required - `entityType` string, required - `parentId` string, nullable, required - `destinationId` string, nullable, required - `timezone` string, required: IANA timezone the park-local days are resolved in. - `range` HistoryRange, required - `from` string, required: The start you asked for. A day comes back as you sent it; an instant comes back normalised to UTC whole seconds. On /history/daily it is always a day. - `to` string, required: The end, in the same form as from. Defaults to today (days) or now (instants). - `coverage` HistoryCoverage, required - `firstRecordedAt` string, date, nullable, required: First park-local day we hold anything for this entity, or null. Per-field detail: GET /v1/entity/{id}/history/coverage. - `days` HistoryDailyRow[], required: One row per day, ascending. Days with no data are left out. - `date` string, date, required: The park-local calendar day this row summarises, YYYY-MM-DD, in the entity's timezone. - `firstOperatingAt` string, date-time, nullable, required: When the entity changed to OPERATING that day (UTC, whole seconds). null when it did not change to OPERATING that day; it may still have operated, carried over from the day before. - `lastClosedAt` string, date-time, nullable, required: When the last run that started this day closed (UTC, whole seconds). A run lasts from a change to OPERATING until the next change to CLOSED or REFURBISHMENT, DOWN periods included. A run still going at midnight closes the next day and is reported on this row. null if it did not close by the end of the next day, or if the close came after 4 hours or more outside published hours with nothing to confirm the run (see unknownMinutes: a change of status on a day with published hours, a change to any field other than showtimes on a day without). - `operatingMinutes` integer, required: Minutes OPERATING with a known status. Today counts elapsed minutes only. CLOSED and REFURBISHMENT minutes are not counted, so operatingMinutes, downMinutes and unknownMinutes need not add up to the day. - `downMinutes` integer, required: Minutes DOWN. Today counts elapsed minutes only. - `unknownMinutes` integer: Minutes with no known status: none was reported, or the entity was OPERATING outside the park's published hours with nothing to confirm it for 4 hours or more. On a day the park published hours, only a change of status confirms it, and a status carried over midnight is unknown outside those hours until it changes. On a day with no published hours, or for an entity outside any park, a change to any field other than showtimes (status, a wait or anything else) confirms it, and for a status carried over midnight the hours count from the last change before midnight. Absent on rows counted under earlier rules. - `standby` HistoryDailyStats: Wait statistics for the day. p50, mean and p90 are weighted by how many minutes each wait was showing; min and max are the extremes of every value posted. Only minutes where the entity was OPERATING (not unknown) and the wait was valid count. A wait is valid during the run and on the day it was posted; the wait showing when a ride opens counts from the opening if it last changed within 24 hours; a wait carried over midnight does not count until it changes. Wait values above 1440 minutes (24 hours) are feed errors and are omitted. So is a reading above the destination's plausibility ceiling (600 minutes, or 300 at the destinations the history notes list), which is counted in the row's `implausibleWaits` instead. Otherwise, a reading of 480 minutes or more stays in these statistics and is counted in the row's `extremeWaits`. Absent when no minute counted. - `min` integer, required: Lowest wait posted during the counted minutes, including one that showed for under a minute. - `p50` integer, required: Median wait, weighted by minutes; always a value that was actually posted. - `mean` integer, required: Minute-weighted average wait, rounded to the nearest whole minute. - `p90` integer, required: 90th-percentile wait, weighted by minutes. - `max` integer, required: Highest wait posted during the counted minutes, including a brief spike. It can be a feed error: the row's extremeWaits counts readings of 480 minutes or more. It never exceeds the destination's plausibility ceiling (see implausibleWaits). - `singleRider` HistoryDailyStats: Wait statistics for the day. p50, mean and p90 are weighted by how many minutes each wait was showing; min and max are the extremes of every value posted. Only minutes where the entity was OPERATING (not unknown) and the wait was valid count. A wait is valid during the run and on the day it was posted; the wait showing when a ride opens counts from the opening if it last changed within 24 hours; a wait carried over midnight does not count until it changes. Wait values above 1440 minutes (24 hours) are feed errors and are omitted. So is a reading above the destination's plausibility ceiling (600 minutes, or 300 at the destinations the history notes list), which is counted in the row's `implausibleWaits` instead. Otherwise, a reading of 480 minutes or more stays in these statistics and is counted in the row's `extremeWaits`. Absent when no minute counted. - `min` integer, required: Lowest wait posted during the counted minutes, including one that showed for under a minute. - `p50` integer, required: Median wait, weighted by minutes; always a value that was actually posted. - `mean` integer, required: Minute-weighted average wait, rounded to the nearest whole minute. - `p90` integer, required: 90th-percentile wait, weighted by minutes. - `max` integer, required: Highest wait posted during the counted minutes, including a brief spike. It can be a feed error: the row's extremeWaits counts readings of 480 minutes or more. It never exceeds the destination's plausibility ceiling (see implausibleWaits). - `extremeWaits` HistoryDailyExtremeWaits: How many wait readings of 480 minutes or more the day had. Such readings are usually feed errors (values like 999); they are counted here as a flag. Those at or below the destination's plausibility ceiling stay in every statistic; those above it are left out and also counted in implausibleWaits. Wait values above 1440 minutes (24 hours) are feed errors and are omitted. Counted per reading while OPERATING. Present only when there were some, and then with both counts. - `standby` integer, required: Standby readings of 480 minutes or more. - `singleRider` integer, required: Single-rider readings of 480 minutes or more. - `implausibleWaits` HistoryDailyImplausibleWaits: How many wait readings above the destination's plausibility ceiling the day had: 600 minutes, or 300 at destinations whose longest genuine waits are far shorter (listed in the history notes). Such a reading is a value the park's feed or app shows that cannot be a real queue (a placeholder like 999, or an unlabelled code); the live API still reports it as the park published it, and the raw history keeps it, but the day's statistics leave it out as if no wait were showing. Counted per reading while OPERATING. Present only when there were some, and then with both counts. - `standby` integer, required: Standby readings above the destination's plausibility ceiling, left out of the day's standby statistics. - `singleRider` integer, required: Single-rider readings above the destination's plausibility ceiling, left out of the day's single-rider statistics. - `showCount` integer: Distinct performance start times whose park-local day is this day. Present only for entities that published showtimes on the day. - `inParkHours` HistoryDailyInParkHours: The day's numbers limited to the park's published hours. Present only when the park published hours that day. - `scheduledMinutes` integer, required: Minutes of the day inside the park's published hours: its schedule entries of type OPERATING, EXTRA_HOURS and TICKETED_EVENT. Hours from the previous day's schedule that run past midnight are not included. Today counts elapsed minutes only. - `operatingMinutes` integer, required: Of scheduledMinutes, the minutes the entity was OPERATING. - `downMinutes` integer, required: Of scheduledMinutes, the minutes the entity was DOWN. - `unknownMinutes` integer, required: Of scheduledMinutes, the minutes with no known status. - `standby` HistoryDailyStats: Wait statistics for the day. p50, mean and p90 are weighted by how many minutes each wait was showing; min and max are the extremes of every value posted. Only minutes where the entity was OPERATING (not unknown) and the wait was valid count. A wait is valid during the run and on the day it was posted; the wait showing when a ride opens counts from the opening if it last changed within 24 hours; a wait carried over midnight does not count until it changes. Wait values above 1440 minutes (24 hours) are feed errors and are omitted. So is a reading above the destination's plausibility ceiling (600 minutes, or 300 at the destinations the history notes list), which is counted in the row's `implausibleWaits` instead. Otherwise, a reading of 480 minutes or more stays in these statistics and is counted in the row's `extremeWaits`. Absent when no minute counted. - `min` integer, required: Lowest wait posted during the counted minutes, including one that showed for under a minute. - `p50` integer, required: Median wait, weighted by minutes; always a value that was actually posted. - `mean` integer, required: Minute-weighted average wait, rounded to the nearest whole minute. - `p90` integer, required: 90th-percentile wait, weighted by minutes. - `max` integer, required: Highest wait posted during the counted minutes, including a brief spike. It can be a feed error: the row's extremeWaits counts readings of 480 minutes or more. It never exceeds the destination's plausibility ceiling (see implausibleWaits). - `singleRider` HistoryDailyStats: Wait statistics for the day. p50, mean and p90 are weighted by how many minutes each wait was showing; min and max are the extremes of every value posted. Only minutes where the entity was OPERATING (not unknown) and the wait was valid count. A wait is valid during the run and on the day it was posted; the wait showing when a ride opens counts from the opening if it last changed within 24 hours; a wait carried over midnight does not count until it changes. Wait values above 1440 minutes (24 hours) are feed errors and are omitted. So is a reading above the destination's plausibility ceiling (600 minutes, or 300 at the destinations the history notes list), which is counted in the row's `implausibleWaits` instead. Otherwise, a reading of 480 minutes or more stays in these statistics and is counted in the row's `extremeWaits`. Absent when no minute counted. - `min` integer, required: Lowest wait posted during the counted minutes, including one that showed for under a minute. - `p50` integer, required: Median wait, weighted by minutes; always a value that was actually posted. - `mean` integer, required: Minute-weighted average wait, rounded to the nearest whole minute. - `p90` integer, required: 90th-percentile wait, weighted by minutes. - `max` integer, required: Highest wait posted during the counted minutes, including a brief spike. It can be a feed error: the row's extremeWaits counts readings of 480 minutes or more. It never exceeds the destination's plausibility ceiling (see implausibleWaits). - `extremeWaits` HistoryDailyExtremeWaits: How many wait readings of 480 minutes or more the day had. Such readings are usually feed errors (values like 999); they are counted here as a flag. Those at or below the destination's plausibility ceiling stay in every statistic; those above it are left out and also counted in implausibleWaits. Wait values above 1440 minutes (24 hours) are feed errors and are omitted. Counted per reading while OPERATING. Present only when there were some, and then with both counts. - `standby` integer, required: Standby readings of 480 minutes or more. - `singleRider` integer, required: Single-rider readings of 480 minutes or more. - `implausibleWaits` HistoryDailyImplausibleWaits: How many wait readings above the destination's plausibility ceiling the day had: 600 minutes, or 300 at destinations whose longest genuine waits are far shorter (listed in the history notes). Such a reading is a value the park's feed or app shows that cannot be a real queue (a placeholder like 999, or an unlabelled code); the live API still reports it as the park published it, and the raw history keeps it, but the day's statistics leave it out as if no wait were showing. Counted per reading while OPERATING. Present only when there were some, and then with both counts. - `standby` integer, required: Standby readings above the destination's plausibility ceiling, left out of the day's standby statistics. - `singleRider` integer, required: Single-rider readings above the destination's plausibility ceiling, left out of the day's single-rider statistics. - `changes` integer, required: How many times any field changed this day. - `next` string, nullable, required: Always null for a single entity. - HistoryParkDailyEnvelope: The daily summary of a whole PARK, returned by /history/daily when the entity's entityType is PARK. A call serves up to 31 park-local days; `range.to` is this page's last day. - `id` string, required - `name` string, required - `entityType` string, required - `parentId` string, nullable, required - `destinationId` string, nullable, required - `timezone` string, required: IANA timezone of the park; every entity is summarised in it. - `range` HistoryRange, required - `from` string, required: The start you asked for. A day comes back as you sent it; an instant comes back normalised to UTC whole seconds. On /history/daily it is always a day. - `to` string, required: The end, in the same form as from. Defaults to today (days) or now (instants). - `entities` HistoryParkEntityDaily[], required: One entry per entity with history, by name. Entities with no history are absent. - `id` string, required - `name` string, required - `entityType` string, required - `coverage` HistoryCoverage, required - `firstRecordedAt` string, date, nullable, required: First park-local day we hold anything for this entity, or null. Per-field detail: GET /v1/entity/{id}/history/coverage. - `days` HistoryDailyRow[], required: The entity's rows for this page, as /history/daily returns them for the entity alone. Empty when it has no data in these days. - `date` string, date, required: The park-local calendar day this row summarises, YYYY-MM-DD, in the entity's timezone. - `firstOperatingAt` string, date-time, nullable, required: When the entity changed to OPERATING that day (UTC, whole seconds). null when it did not change to OPERATING that day; it may still have operated, carried over from the day before. - `lastClosedAt` string, date-time, nullable, required: When the last run that started this day closed (UTC, whole seconds). A run lasts from a change to OPERATING until the next change to CLOSED or REFURBISHMENT, DOWN periods included. A run still going at midnight closes the next day and is reported on this row. null if it did not close by the end of the next day, or if the close came after 4 hours or more outside published hours with nothing to confirm the run (see unknownMinutes: a change of status on a day with published hours, a change to any field other than showtimes on a day without). - `operatingMinutes` integer, required: Minutes OPERATING with a known status. Today counts elapsed minutes only. CLOSED and REFURBISHMENT minutes are not counted, so operatingMinutes, downMinutes and unknownMinutes need not add up to the day. - `downMinutes` integer, required: Minutes DOWN. Today counts elapsed minutes only. - `unknownMinutes` integer: Minutes with no known status: none was reported, or the entity was OPERATING outside the park's published hours with nothing to confirm it for 4 hours or more. On a day the park published hours, only a change of status confirms it, and a status carried over midnight is unknown outside those hours until it changes. On a day with no published hours, or for an entity outside any park, a change to any field other than showtimes (status, a wait or anything else) confirms it, and for a status carried over midnight the hours count from the last change before midnight. Absent on rows counted under earlier rules. - `standby` HistoryDailyStats: Wait statistics for the day. p50, mean and p90 are weighted by how many minutes each wait was showing; min and max are the extremes of every value posted. Only minutes where the entity was OPERATING (not unknown) and the wait was valid count. A wait is valid during the run and on the day it was posted; the wait showing when a ride opens counts from the opening if it last changed within 24 hours; a wait carried over midnight does not count until it changes. Wait values above 1440 minutes (24 hours) are feed errors and are omitted. So is a reading above the destination's plausibility ceiling (600 minutes, or 300 at the destinations the history notes list), which is counted in the row's `implausibleWaits` instead. Otherwise, a reading of 480 minutes or more stays in these statistics and is counted in the row's `extremeWaits`. Absent when no minute counted. - `min` integer, required: Lowest wait posted during the counted minutes, including one that showed for under a minute. - `p50` integer, required: Median wait, weighted by minutes; always a value that was actually posted. - `mean` integer, required: Minute-weighted average wait, rounded to the nearest whole minute. - `p90` integer, required: 90th-percentile wait, weighted by minutes. - `max` integer, required: Highest wait posted during the counted minutes, including a brief spike. It can be a feed error: the row's extremeWaits counts readings of 480 minutes or more. It never exceeds the destination's plausibility ceiling (see implausibleWaits). - `singleRider` HistoryDailyStats: Wait statistics for the day. p50, mean and p90 are weighted by how many minutes each wait was showing; min and max are the extremes of every value posted. Only minutes where the entity was OPERATING (not unknown) and the wait was valid count. A wait is valid during the run and on the day it was posted; the wait showing when a ride opens counts from the opening if it last changed within 24 hours; a wait carried over midnight does not count until it changes. Wait values above 1440 minutes (24 hours) are feed errors and are omitted. So is a reading above the destination's plausibility ceiling (600 minutes, or 300 at the destinations the history notes list), which is counted in the row's `implausibleWaits` instead. Otherwise, a reading of 480 minutes or more stays in these statistics and is counted in the row's `extremeWaits`. Absent when no minute counted. - `min` integer, required: Lowest wait posted during the counted minutes, including one that showed for under a minute. - `p50` integer, required: Median wait, weighted by minutes; always a value that was actually posted. - `mean` integer, required: Minute-weighted average wait, rounded to the nearest whole minute. - `p90` integer, required: 90th-percentile wait, weighted by minutes. - `max` integer, required: Highest wait posted during the counted minutes, including a brief spike. It can be a feed error: the row's extremeWaits counts readings of 480 minutes or more. It never exceeds the destination's plausibility ceiling (see implausibleWaits). - `extremeWaits` HistoryDailyExtremeWaits: How many wait readings of 480 minutes or more the day had. Such readings are usually feed errors (values like 999); they are counted here as a flag. Those at or below the destination's plausibility ceiling stay in every statistic; those above it are left out and also counted in implausibleWaits. Wait values above 1440 minutes (24 hours) are feed errors and are omitted. Counted per reading while OPERATING. Present only when there were some, and then with both counts. - `standby` integer, required: Standby readings of 480 minutes or more. - `singleRider` integer, required: Single-rider readings of 480 minutes or more. - `implausibleWaits` HistoryDailyImplausibleWaits: How many wait readings above the destination's plausibility ceiling the day had: 600 minutes, or 300 at destinations whose longest genuine waits are far shorter (listed in the history notes). Such a reading is a value the park's feed or app shows that cannot be a real queue (a placeholder like 999, or an unlabelled code); the live API still reports it as the park published it, and the raw history keeps it, but the day's statistics leave it out as if no wait were showing. Counted per reading while OPERATING. Present only when there were some, and then with both counts. - `standby` integer, required: Standby readings above the destination's plausibility ceiling, left out of the day's standby statistics. - `singleRider` integer, required: Single-rider readings above the destination's plausibility ceiling, left out of the day's single-rider statistics. - `showCount` integer: Distinct performance start times whose park-local day is this day. Present only for entities that published showtimes on the day. - `inParkHours` HistoryDailyInParkHours: The day's numbers limited to the park's published hours. Present only when the park published hours that day. - `scheduledMinutes` integer, required: Minutes of the day inside the park's published hours: its schedule entries of type OPERATING, EXTRA_HOURS and TICKETED_EVENT. Hours from the previous day's schedule that run past midnight are not included. Today counts elapsed minutes only. - `operatingMinutes` integer, required: Of scheduledMinutes, the minutes the entity was OPERATING. - `downMinutes` integer, required: Of scheduledMinutes, the minutes the entity was DOWN. - `unknownMinutes` integer, required: Of scheduledMinutes, the minutes with no known status. - `standby` HistoryDailyStats: Wait statistics for the day. p50, mean and p90 are weighted by how many minutes each wait was showing; min and max are the extremes of every value posted. Only minutes where the entity was OPERATING (not unknown) and the wait was valid count. A wait is valid during the run and on the day it was posted; the wait showing when a ride opens counts from the opening if it last changed within 24 hours; a wait carried over midnight does not count until it changes. Wait values above 1440 minutes (24 hours) are feed errors and are omitted. So is a reading above the destination's plausibility ceiling (600 minutes, or 300 at the destinations the history notes list), which is counted in the row's `implausibleWaits` instead. Otherwise, a reading of 480 minutes or more stays in these statistics and is counted in the row's `extremeWaits`. Absent when no minute counted. - `min` integer, required: Lowest wait posted during the counted minutes, including one that showed for under a minute. - `p50` integer, required: Median wait, weighted by minutes; always a value that was actually posted. - `mean` integer, required: Minute-weighted average wait, rounded to the nearest whole minute. - `p90` integer, required: 90th-percentile wait, weighted by minutes. - `max` integer, required: Highest wait posted during the counted minutes, including a brief spike. It can be a feed error: the row's extremeWaits counts readings of 480 minutes or more. It never exceeds the destination's plausibility ceiling (see implausibleWaits). - `singleRider` HistoryDailyStats: Wait statistics for the day. p50, mean and p90 are weighted by how many minutes each wait was showing; min and max are the extremes of every value posted. Only minutes where the entity was OPERATING (not unknown) and the wait was valid count. A wait is valid during the run and on the day it was posted; the wait showing when a ride opens counts from the opening if it last changed within 24 hours; a wait carried over midnight does not count until it changes. Wait values above 1440 minutes (24 hours) are feed errors and are omitted. So is a reading above the destination's plausibility ceiling (600 minutes, or 300 at the destinations the history notes list), which is counted in the row's `implausibleWaits` instead. Otherwise, a reading of 480 minutes or more stays in these statistics and is counted in the row's `extremeWaits`. Absent when no minute counted. - `min` integer, required: Lowest wait posted during the counted minutes, including one that showed for under a minute. - `p50` integer, required: Median wait, weighted by minutes; always a value that was actually posted. - `mean` integer, required: Minute-weighted average wait, rounded to the nearest whole minute. - `p90` integer, required: 90th-percentile wait, weighted by minutes. - `max` integer, required: Highest wait posted during the counted minutes, including a brief spike. It can be a feed error: the row's extremeWaits counts readings of 480 minutes or more. It never exceeds the destination's plausibility ceiling (see implausibleWaits). - `extremeWaits` HistoryDailyExtremeWaits: How many wait readings of 480 minutes or more the day had. Such readings are usually feed errors (values like 999); they are counted here as a flag. Those at or below the destination's plausibility ceiling stay in every statistic; those above it are left out and also counted in implausibleWaits. Wait values above 1440 minutes (24 hours) are feed errors and are omitted. Counted per reading while OPERATING. Present only when there were some, and then with both counts. - `standby` integer, required: Standby readings of 480 minutes or more. - `singleRider` integer, required: Single-rider readings of 480 minutes or more. - `implausibleWaits` HistoryDailyImplausibleWaits: How many wait readings above the destination's plausibility ceiling the day had: 600 minutes, or 300 at destinations whose longest genuine waits are far shorter (listed in the history notes). Such a reading is a value the park's feed or app shows that cannot be a real queue (a placeholder like 999, or an unlabelled code); the live API still reports it as the park published it, and the raw history keeps it, but the day's statistics leave it out as if no wait were showing. Counted per reading while OPERATING. Present only when there were some, and then with both counts. - `standby` integer, required: Standby readings above the destination's plausibility ceiling, left out of the day's standby statistics. - `singleRider` integer, required: Single-rider readings above the destination's plausibility ceiling, left out of the day's single-rider statistics. - `changes` integer, required: How many times any field changed this day. - `next` string, nullable, required: Absolute URL of the next page (your parameters kept, `from` moved on), or null on the last page. Up to 31 park-local days a page. ## Other responses - `400`: Bad request - `403`: Access forbidden - `404`: Resource not found - `429`: Too many requests ## Changes - **2026-10-02** `52d00dcd203a`: 4 info - added the optional property `oneOf[#/components/schemas/HistoryDailyEnvelope]/days/items/implausibleWaits` to the response with the `200` status - added the optional property `oneOf[#/components/schemas/HistoryDailyEnvelope]/days/items/inParkHours/implausibleWaits` to the response with the `200` status - added the optional property `oneOf[#/components/schemas/HistoryParkDailyEnvelope]/entities/items/days/items/implausibleWaits` to the response with the `200` status - added the optional property `oneOf[#/components/schemas/HistoryParkDailyEnvelope]/entities/items/days/items/inParkHours/implausibleWaits` to the response with the `200` status - **2026-09-27** `f12e25418ddc`: 3 breaking, 6 info - added `#/components/schemas/HistoryErrorRateLimited, #/components/schemas/RateLimited` to the response body `oneOf` list for the response status `429` - the response's body type changed from `object` to no type for status `429` - removed the required property `error` from the response with the `429` status - added the optional property `oneOf[#/components/schemas/HistoryDailyEnvelope]/days/items/extremeWaits` to the response with the `200` status - …5 more - …earlier changes not shown [Operation history](https://skmtc.dev/themeparks/apis/v1-api/changes/v1/entity/:id/history/daily/get.md) --- [API](https://skmtc.dev/themeparks/apis/v1-api.md) - [All operations](https://skmtc.dev/themeparks/apis/v1-api/llms.txt) - [OpenAPI document](https://skmtc.dev/themeparks/apis/v1-api/revisions/a9f0cb93c745?raw)