Skip to main content
POST
Add organization member

Authorizations

Authorization
string
header
required

API key sent in the Authorization header, with no Bearer prefix.

Path Parameters

organizationId
string<uuid>
required

The organization this call acts for: your API key's organization or one of its customer organizations. Any other id returns 404 not-found.

Body

application/json
role
enum<string>
required

The member's role in the organization.

Available options:
admin,
member
email
string | null

Invite or add a member by email address. If the email matches a user who has already signed in through your JWT, they're added as a member immediately; otherwise a pending invite is created and accepted automatically the first time that email signs in via your kyb JWT. Use email when you don't have the person's memberId yet, or when you want Etherfuse to email them an invite (see emailInviteLink). Send exactly one of email or memberId.

memberId
string | null

Add someone directly by their sub (the value you put in the JWT sub when they sign in); no email is sent. The person must already exist, which happens the first time they exchange a JWT via POST /auth/token (or are launched); an unknown sub returns 404. A business organization's id is rejected. Send exactly one of email or memberId.

Optional. When adding by email and a pending invite is created (the email isn't already a member), Etherfuse emails them this URL as-is (you control the full link, including any query params) as the call to action. Omit it to create the invite silently and notify the user yourself. Ignored when the email already matches a member who is added immediately.

Response

The organization's members and pending invites after the change.

members
object[]
required

Active members. The org's own service account is never listed.

invited
object[]
required

Pending invites that have not been accepted yet.