Change a member's role
Authorization
OAuth2PasswordBearer In: header
Path Parameters
uuidCookie Parameters
Request Body
application/json
TypeScript Definitions
Use the request body type in TypeScript.
Change what a member may do. IN-302.
Response Body
application/json
application/json
curl -X PATCH "https://example.com/api/b/v1/members/497f6eca-6276-4993-bfeb-53cbbbba6f08/role" \ -H "Content-Type: application/json" \ -d '{ "role": "finance" }'{ "id": "497f6eca-6276-4993-bfeb-53cbbbba6f08", "user_id": "a169451c-8525-4352-b8ca-070dd449a1a5", "role": "owner", "status": "invited", "invited_by": "0fdabe0c-eb7c-440a-96d2-2c65906c3777", "full_name": "string", "email": "string", "phone_number": "string"}Accept an invitation addressed to you POST
Accepting is the invited person's own act — IN-341. **This takes a plain signed-in user, not a business context, and that is the whole fix.** It used to depend on `require_permission`, which resolves through `get_business_context`, which refuses a member who is not yet ACTIVE. The only way to become scoped to a business is `/context/switch`, which refuses that same member with "Accept your invitation first". The endpoint could only ever be reached by somebody who had already accepted. The token identifies both the invitation and the business, so nothing is taken from the caller but their identity.
Suspend or reinstate a member PATCH
Next Page