List free times
The times a customer can book a service, for one day or up to 14 in a row. Leave staff_id out to get the free times of everyone who does the service. A slot is free now and may be gone a moment later: booking it answers 409 slot_taken when someone was faster.
Keys: every kind of key works here.
apiKeyAuthorizationBearer wo_live_...A key from the shop's admin. Secret keys start with wo_live_, public keys with wo_pub_.
date*stringThe first day, as the shop's own calendar has it: 2026-11-30.
length <= 10days?integerHow many days from date on.
1 <= value <= 141service_id*stringThe service to book.
uuidstaff_id?stringOnly this staff member's free times.
uuidThe request worked.
application/json- response
data*array<>has_more*booleanWhether another page follows this one.
next_cursor*|nullobject*stringcurl 'https://api.weerom.com/v1/availability?date=string&service_id=497f6eca-6276-4993-bfeb-53cbbbba6f08'{ "data": [ { "ends_at": "2026-11-30T09:45:00.000Z", "object": "slot", "service_id": "c2a41f6e-8d3b-4e97-b5a0-1f7c9e2d4a68", "staff_id": "8e1d5b7c-3a9f-4d20-b6c4-7a2e0f9d1c53", "starts_at": "2026-11-30T09:00:00.000Z" } ], "has_more": false, "next_cursor": null, "object": "list"}Details
Keys
Read keyWrite keyPublic key
Every kind of key may call it.
Sort
By starts_at, earliest first, then by staff_id. The order is fixed.
Filters
dateis a day on the shop's own calendar, not a UTC day. Withdays, the list covers that day and the days after it,daysin all.staff_idkeeps one person's times. A staff member who is inactive, unknown or does not do the service gives an empty list, not an error.
What it does
- The times are the ones the shop's own booking form offers: its opening hours, each person's hours and breaks, bookings already made, and the lead time. Times that have passed are left out.
- Without
staff_id, the list holds the times of every active staff member who does the service. One time can show up once per person. - The whole list fits on one page:
has_moreisfalseandnext_cursorisnull. The list takes nolimit,cursorororder, and sending one answers 400invalid_request.
Errors
Besides 401 for a missing, unknown or removed key, 403 plan_required, 429 rate_limited and 500 internal_error, which every endpoint can answer. Errors has all of them.
| Status | code | When | What to do |
|---|---|---|---|
| 400 | invalid_request | date is not a day, days is out of range, or service_id is missing. | Send date as a day such as 2026-11-30 and days from 1 to 14. |
| 404 | not_found | The service does not exist or is inactive. | Read GET /services and pick an active service. |
Get a staff member GET
One staff member by their id. **Keys:** every kind of key works here.
List customers GET
Customers sorted by when the shop first saw them. Filter by `email` or `phone` to look one up, or by `updated_after` to fetch what changed since your last sync. **Keys:** a key that may read. A public key gets 403.