List bookable members
GET/api/v1/bookable-members
scope
bookings:readThe team members who can be booked. A member appears here once they have working hours; someone who has never set any produces no slots and is left out.
Request
curl "https://your-crm.example.com/api/v1/bookable-members" \
-H "Authorization: Bearer $RAABTA_API_KEY"Response · 200 OK
{
"data": [
{
"user_id": "2f3e4d5c-6b7a-4c8d-9e0f-1a2b3c4d5e6f",
"name": "Sara Ahmed",
"headline": "Senior consultant",
"avatar_url": null,
"color": "#3b82f6"
}
]
}Response
Wrapped in { data: … }| Name | Type | Description |
|---|---|---|
user_idrequired | string (uuid) | Pass as assignee_user_id when booking |
namerequired | string | The member’s display name |
headlinerequired | string | null | A short line shown beside the name |
avatar_urlrequired | string | null | The member’s photo, when they have one |
colorrequired | string | null | Hex colour used on the calendar |
Errors
| Status | Code | When |
|---|---|---|
| 401 | unauthorized | No usable API key: the Authorization header is missing or malformed, or the key is unknown, revoked or expired. The three are deliberately indistinguishable. |
| 403 | forbidden | The key is valid but lacks the scope this endpoint requires, or the request came from an address outside the key’s IP allowlist. The message says which. |
| 403 | account_suspended | The account this key belongs to is suspended. Rotating the key will not help; contact support. |
| 422 | unprocessable | The request was well-formed but cannot be carried out. `reason` is a stable string saying why (for example `outside_window` or `stage_not_in_pipeline`). |
| 429 | rate_limited | The per-key budget, or the per-IP budget for failed authentication, is exhausted. Honour `Retry-After` before retrying. |
| 500 | internal | Something failed on our side. Safe to retry with the same Idempotency-Key; quote `request_id` if it persists. |