Skip to main content
GET
Get Member

Authorizations

Authorization
string
header
required

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

Thinnest-Workspace
string

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"

Path Parameters

id
string<uuid>
required

The member's id, from List Members.

Response

The member.

id
string<uuid>
required

The person's id, used by Update Member, Remove Member and Add Team Member.

Example:

"1f3a5c7e-9b2d-4e6f-8a0c-2e4f6a8b0d13"

name
string
required

Their name.

Example:

"Rahul Kulkarni"

email
string<email>
required

Their sign-in email.

Example:

"rahul@sunrisedental.in"

role
enum<string>
required

owner, admin or member.

Available options:
owner,
admin,
member
Example:

"member"

joinedAt
string<date-time> | null
required

When they joined the workspace.

Example:

"2026-09-03T12:48:09.377Z"