Guides
Wait history
What a place's posted waits were: hourly or daily averages, or every reading. History describes the past; it never predicts a visit.
Ask for history
Call GET /v1/places/{id}/history with a place id, or the get_history tool. Without from and to it returns the last 7 days, hour by hour.
curl "https://api.waity.ai/v1/places/pl_xaed7pr1f5/history?granularity=day&from=2026-10-01" \
-H "X-Api-Key: $WAITY_API_KEY"
Granularity
hour | One row per hour with data: avg, median, p90, min, max, the number of posted updates and the share of the hour the place was open. |
day | One row per local day, the same figures weighted by open time. |
raw | Every posted reading, with its time, bound, basis and source. |
Ranges and pages
from and to take a date (local to the place) or an ISO date-time; a date in to means the end of that day. Long ranges come in pages: pass cursor from page.next_cursor to get the next one.
How far back
History needs a key. A range wider than your plan reads is clipped, not refused: range.clipped is true and the answer says so.
| Plan | Reads back |
|---|---|
| Free | 30 days |
| Plus | 365 days |
| Pro | 365 days |
| Team | Everything |
ER history
Past ER waits describe what was posted then. They don't predict a visit now: in an emergency, go to the nearest ER or call 911.