Skip to main content
A member is a person in a Fluid company — a customer, a rep, or a type the company defines. Fluid has two sets of member endpoints, and which one you use depends on who is calling:

​
The member API

The member API acts as the signed-in member. The credential alone decides which member and which company a request is about — no path, query, or body parameter ever names a member.

​
Credentials

Send the member’s credential as a Bearer token to https://api.fluid.app:
A member credential is a member session JWT, a portal JWT whose login is linked to a membership in that company, or a member token. The member API refuses, with 401:
  • Company, partner, public (pub-), and droplet installation tokens.
  • Any credential belonging to a company admin — including an admin who is also a member of that company.
  • A credential for a member who is removed, inactive, or locked, or whose company is inactive.
A JWT that can also travel in a URL is read-only: a write with it returns 403.

​
Identity and memberships

​
Team

A member can read their own team — the part of their company’s genealogy below them — and request moves within it:
  • Team reads are limited to the member’s current team. A member never sees seats outside it.
  • Moves take effect on the server’s clock. An immediate move returns 200. A move that needs approval, or runs later as a job, returns 202 with a receipt you can follow.
  • A company has to enable moves. Until it does, move requests are refused.
The team endpoints accept a member or customer session JWT, or a member’s user token. Company tokens are refused.
The member API currently covers identity, memberships, and team. Other member data — such as a member’s orders or contacts — isn’t available through it yet.

​
Member management

These endpoints are in the People section of the API reference, under Members. A company manages its members with a company token that has the members permission: Use these endpoints rather than the older customer and member endpoints listed with them when the member’s type matters: only member management returns member_type. To manage the company’s genealogy trees themselves — defining trees, placing members, and approving moves — use the Genealogy endpoints in the People section of the API reference, with a company token.