Team Members

List team members, retrieve individual profiles, and check real-time availability for assignment decisions.

List team members

GET /v1/team/members

Prop	Type	Default
`is_active`	`boolean`	-
`team_id`	`string`	-
`skills`	`string`	-
`limit`	`integer`	`50`
`offset`	`integer`	`0`

curl "https://api.slatis.com/v1/team/members?is_active=true&skills=javascript&limit=20" \
  -H "Authorization: Bearer sk_live_xxx"

{
  "success": true,
  "members": [
    {
      "object": "team_member",
      "id": "mem_01abc",
      "name": "Alex Rivera",
      "email": "alex@example.com",
      "avatar_url": null,
      "role": "MEMBER",
      "skills": ["javascript", "react"],
      "is_active": true,
      "team": { "id": "team_01", "name": "Engineering" }
    }
  ],
  "pagination": { "total": 12, "limit": 20, "offset": 0, "has_more": false }
}

Get a specific member

GET /v1/team/members/{id}

Returns the same shape as a single item from the list, plus any additional profile fields.

Get available members

Returns team members who have availability on a specific date:

GET /v1/team/members/available?date=2026-05-01&duration=30

Prop	Type	Default
`date`	`YYYY-MM-DD`	-
`duration`	`integer`	`30`
`team_id`	`string`	-
`skills`	`string`	-

Each member includes an availability block with booking counts and next open date for fully-booked members.

This endpoint uses team:read, which publishable keys may hold, so it returns no names, emails or avatars. Pass id straight to assign_to when creating a booking; to put a name on it, call GET /team/members/{id} with a secret key holding team:members:read.

{
  "success": true,
  "members": [
    {
      "object": "team_member",
      "id": "mem_01abc",
      "role": "MEMBER",
      "skills": ["javascript", "react"],
      "is_active": true,
      "team": { "id": "team_01", "name": "Engineering" },
      "availability": {
        "is_available": true,
        "next_available_slot": null,
        "booked_slots": 3,
        "max_bookings_per_day": 8
      }
    }
  ],
  "date": "2026-05-01",
  "pagination": { "total": 5, "limit": 50, "offset": 0, "has_more": false }
}

Assign a booking to a specific member

Pass assign_to (team member ID) when creating a booking to bypass the routing algorithm. The member's calendar availability is still validated.

{
  "event_type_id": "evt_01abc",
  "attendee": { "name": "Jane", "email": "jane@example.com" },
  "requested_time": "2026-05-01T14:00:00Z",
  "assign_to": "mem_01xyz"
}

List team members

Get a specific member

Get available members

Assign a booking to a specific member

On this page