Skip to Content
Developers
Staff

List staff

GET
/staff

Everyone customers can book with, in the shop's order.

Keys: every kind of key works here.

Authorization

apiKey
headerAuthorizationBearer wo_live_...

A key from the shop's admin. Secret keys start with wo_live_, public keys with wo_pub_.

Query parameters

active?boolean

Only active ones, or only inactive ones.

Response body

The request worked.

application/json
  1. response
data*array<>
has_more*boolean

Whether another page follows this one.

next_cursor*|null
object*string
Example request
curl 'https://api.weerom.com/v1/staff'
Example response
{  "data": [    {      "active": true,      "created_at": "2026-03-02T08:15:00.000Z",      "id": "8e1d5b7c-3a9f-4d20-b6c4-7a2e0f9d1c53",      "name": "Sam",      "object": "staff",      "service_ids": [        "c2a41f6e-8d3b-4e97-b5a0-1f7c9e2d4a68"      ],      "updated_at": "2026-03-02T08:15:00.000Z"    }  ],  "has_more": false,  "next_cursor": null,  "object": "list"}

Details

Keys

Read keyWrite keyPublic key

Every kind of key may call it.

Sort

In the order the shop shows its staff, then by id. The order is fixed.

Filters

  • active=true keeps the people customers can book. active=false keeps the ones who left the agenda. Leave it out for both.

What it does

  • The whole list fits on one page: has_more is false and next_cursor is null. The list takes no limit, cursor or order, and sending one answers 400 invalid_request.
  • service_ids is sorted by id, not in the shop's order of services.