Check provider wait times

Read current wait times and contribute observations
View as MarkdownOpen in Claude

This guide shows how to read the current wait time for a location and how a member client can contribute a wait-time observation. Both calls are member-path calls; authenticate as a member client first. See Authentication.

Read the wait time for a location

Call GET /v1/wait-times/{locationId} with the stable identifier of the location.

$curl --get "$CAIL_API_BASE_URL/v1/wait-times/8f3c1b2a-4d5e-46c7-b890-1f2e3d4c5b6a" \
> --header "Authorization: Bearer $CAIL_TOKEN"

The response is shaped for the audience that calls it. A member token returns the member view: a current wait-time estimate suitable to show in a client. An operator token returns the operator view, which adds percentile detail for performance monitoring.

Use the member view to set expectations before a member travels, and pair it with Find providers near a member so a member can weigh distance against how busy each option is.

Contribute a wait-time observation

Member clients can submit what a member observed on arrival. These observations keep estimates current. Call POST /v1/wait-times.

$curl --request POST "$CAIL_API_BASE_URL/v1/wait-times" \
> --header "Authorization: Bearer $CAIL_TOKEN" \
> --header "Content-Type: application/json" \
> --data '{
> "locationId": "8f3c1b2a-4d5e-46c7-b890-1f2e3d4c5b6a",
> "valueMinutes": 35,
> "devicePlatform": "ios"
> }'

Observations are anonymous, like every member-path call. Never include a name, contact detail, or other identifying field. See the Auth model for why member flows carry no identifying information.

Next steps