One day's queue
Every queue visit at a location on a single date.
GET /v1/qms-appointments/day-visitsOne day rather than a page of history — what a front desk would have on screen.
API-key only (a widget session is refused) and entitlement-gated on devapi_qms_day_visits.
Query parameters
| Name | Required | Description |
|---|---|---|
addressId | No | A clinic location, from GET /v1/addresses. |
date | No | YYYY-MM-DD |
doctorId | No | A practitioner's medos user id, from GET /v1/doctors. |
Try it
/v1/qms-appointments/day-visitsAPI key onlydevapi_qms_day_visitsQuery
GET /v1/qms-appointments/day-visits?addressId=1&date=2026-10-12https://api.medos.oneUse a dedicated test key, and put your browser's address on its allowlist
A Developer API key authenticates on its own, so it only works from the addresses registered against it — and this page calls from your browser, not your servers. Unless your own public address is on the list you get a 403 naming it, which is the allowlist doing its job. Your browser may also reach us over IPv6 even when your server does not, so the address in the error is often not the one you expected. The key here is kept in memory only and never written to storage, but create a test key for it and deactivate that key when you are done.
Request
curl -sG "https://api.medos.one/v1/qms-appointments/day-visits" \
-H "x-api-key: $MEDOS_API_KEY" \
--data-urlencode "addressId=1" \
--data-urlencode "date=2026-10-12"Common failures
| Status | Cause |
|---|---|
403 with requiredFeature | Not entitled to this operation. |
403 "only available to Developer API keys" | A widget session token was used. Send x-api-key. |