List Members
curl --request GET \
--url https://app.thinnest.ai/api/v1/members \
--header 'Authorization: Bearer <token>'const options = {method: 'GET', headers: {Authorization: 'Bearer <token>'}};
fetch('https://app.thinnest.ai/api/v1/members', options)
.then(res => res.json())
.then(res => console.log(res))
.catch(err => console.error(err));import requests
url = "https://app.thinnest.ai/api/v1/members"
headers = {"Authorization": "Bearer <token>"}
response = requests.get(url, headers=headers)
print(response.text){
"items": [
{
"id": "8c0d2f6e-4a1b-4c3d-9e7f-5b6a0d1c2e34",
"name": "Priya Deshmukh",
"email": "priya@sunrisedental.in",
"role": "owner",
"joinedAt": "2026-08-14T05:22:31.904Z"
},
{
"id": "1f3a5c7e-9b2d-4e6f-8a0c-2e4f6a8b0d13",
"name": "Rahul Kulkarni",
"email": "rahul@sunrisedental.in",
"role": "member",
"joinedAt": "2026-09-03T12:48:09.377Z"
}
],
"nextCursor": null
}{
"error": "Send a valid API key as `Authorization: Bearer <key>`."
}{
"error": "Over 240 requests a minute. Slow down and retry."
}Members
List Members
Everybody in the workspace, with their role — so a conversation can be assigned by email, or a role changed or a person removed by id. Not paged: every member is in one answer, and nextCursor is always null. Pending invitations are listed by List Invitations.
GET
/
members
List Members
curl --request GET \
--url https://app.thinnest.ai/api/v1/members \
--header 'Authorization: Bearer <token>'const options = {method: 'GET', headers: {Authorization: 'Bearer <token>'}};
fetch('https://app.thinnest.ai/api/v1/members', options)
.then(res => res.json())
.then(res => console.log(res))
.catch(err => console.error(err));import requests
url = "https://app.thinnest.ai/api/v1/members"
headers = {"Authorization": "Bearer <token>"}
response = requests.get(url, headers=headers)
print(response.text){
"items": [
{
"id": "8c0d2f6e-4a1b-4c3d-9e7f-5b6a0d1c2e34",
"name": "Priya Deshmukh",
"email": "priya@sunrisedental.in",
"role": "owner",
"joinedAt": "2026-08-14T05:22:31.904Z"
},
{
"id": "1f3a5c7e-9b2d-4e6f-8a0c-2e4f6a8b0d13",
"name": "Rahul Kulkarni",
"email": "rahul@sunrisedental.in",
"role": "member",
"joinedAt": "2026-09-03T12:48:09.377Z"
}
],
"nextCursor": null
}{
"error": "Send a valid API key as `Authorization: Bearer <key>`."
}{
"error": "Over 240 requests a minute. Slow down and retry."
}Authorizations
Your API key (ta_live_…) from Settings → API keys, sent as Authorization: Bearer <key>. Keep it on a server: it can message every customer you have. A key is full, build or read-only; a request its level does not allow is refused with 403.
Headers
Developers only: the customer workspace this request acts in — its org_… id from POST /customers. Leave it out to act in your own workspace.
Example:
"org_3fKq9TzQ1mN8vB2xR7cLpA"