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. A request for a record the member doesn’t own returns 404.

Credentials

Send the member’s credential as a Bearer token to https://api.fluid.app:
A member credential is one of:
  • A member token.
  • A member session JWT.
  • A portal JWT whose login is linked to a membership in that company.
The member API refuses, with 401:
  • Company, partner, public (pub-), and droplet installation tokens.
  • Impersonation credentials, and an admin’s login when that person has no membership of their own in the company.
  • A member token or member session JWT for a member who is also an admin of that company. The exception is the team reads (see Team).
  • A credential for a member who is removed, inactive, or locked, or whose company is inactive.
A portal JWT from an admin’s or a root admin’s login acts as that person’s own membership in the company: the member with the same email address. Their member type then decides which areas they reach. Member tokens and portal JWTs can read and write. Member session JWTs are read-only, and so is a portal JWT issued as read-only: a write with one returns 403. Two more limits apply:
  • Some areas depend on the membership. A valid credential for a membership without access gets 403:
    • Contacts, groups, notes, tasks, messaging, and the team list are for the rep member type. Any other membership gets 403, including a type the company defines.
    • Media and sharing, asset statistics, the AI assistant, and My Site are for members whose member type has Can act as rep turned on. Other memberships get 403.
    • Catalog search, the statistics dashboard, and the activity feed are open to every membership.
  • A member session JWT reads only part of the API. That JWT also travels in order and subscription email links. Contacts, groups, notes, tasks, messaging, AI conversations, statistics, push devices, and the team list refuse it with 403. Use a member token or a portal JWT. The member’s own orders, subscriptions, and activity feed still accept a member session JWT.

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.
  • The team list and the seats use different ids. The team list identifies each person by member id. The seat, tree, and move operations take seat ids.
  • 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.
  • Moves stay inside the member’s downline. The member’s own seat can’t be moved. Only a member whose type has Can act as rep turned on can request a move.
  • A company has to enable moves. Until it does, move requests are refused.
The team endpoints follow the same credential rules as the rest of the member API, including the read-only JWTs: a move request with a member session JWT returns 403. The team list and summary are for reps, and refuse a member session JWT. One exception: a member whose user is also an admin of the same company, such as an owner who is also a rep, can read their own team with their own member token. They can’t request moves with it.

Everything else

The member API also covers the rest of what a member does in their own app or portal. Each area has its own section in the API reference: For live messaging, call Admit a realtime socket first. It returns a ticket that opens one socket within one minute, so the member’s credential never goes in a socket URL. Get a new ticket each time you connect.

Contacts

A rep keeps their own contacts in Fluid, and organizes them with groups, notes, and tasks. These operations are for the rep member type, and refuse a member session JWT.

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.