DocumentationAPI reference
Rust · 0.1.0
Space Service
Create collaborative spaces, manage their members and complete invitation lifecycles.
Use space roles
Any authenticated user can create a space and becomes its first ADMIN. Listing, viewing and member lookup require active membership. Metadata changes, invitations and other members' removal require the space ADMIN role. Instance ADMIN is not a substitute for space membership or governance. A pending invitation is not membership; only its invitee can accept or decline it. A space must keep an active administrator.
Operations
- GETList Spaces
/api/v1/spaces - POSTCreate Space
/api/v1/spaces - GETGet Space
/api/v1/spaces/{space} - DELETEDelete Space
/api/v1/spaces/{space} - PATCHUpdate Space
/api/v1/spaces/{space} - GETList Space Invitations
/api/v1/spaces/{space}/invitations - POSTCreate Space Invitation
/api/v1/spaces/{space}/invitations - GETGet Space Invitation
/api/v1/spaces/{space}/invitations/{invitation} - DELETEDelete Space Invitation
/api/v1/spaces/{space}/invitations/{invitation} - POSTAccept Space Invitation
/api/v1/spaces/{space}/invitations/{invitation}:accept - POSTDecline Space Invitation
/api/v1/spaces/{space}/invitations/{invitation}:decline - GETList Space Members
/api/v1/spaces/{space}/members - GETGet Space Member
/api/v1/spaces/{space}/members/{member} - DELETEDelete Space Member
/api/v1/spaces/{space}/members/{member} - PATCHUpdate Space Member
/api/v1/spaces/{space}/members/{member} - GETList User Space Invitations
/api/v1/users/{user}/spaceInvitations