Delete Space
Deletes a space by ID.
The token needs the Manager role on that Space, whatever its general access: a client-credentials token through a role given to its client, which the organization registered, a token issued for a user through that user's role, and that user must be an admin or owner of the organization. Without it, the request answers 403 with the code FORBIDDEN and the reason ROLE_REQUIRED, and nothing is deleted.
bearerAuthAutorisatieBearer <token>space_id*stringID of the Space
Space deleted
curl -X DELETE 'https://api.tibata.ai/v1/spaces/string'Update Space PATCH
Updates a space by ID. When not every member can edit the Space (general access Can view or No access), the token needs the Editor or Manager role on that Space: a client-credentials token through a role given to its client, a token issued for a user through that user's role. Without it, the request answers `403` with the code `FORBIDDEN` and the reason `ROLE_REQUIRED`, and nothing changes. A name or slug another Space already uses answers `409` with the code `CONFLICT` and the reason `NAME_TAKEN` or `SLUG_TAKEN`. When someone else changes the Space while the request is being saved, it answers `409` with the reason `CHANGED`, and nothing changes: fetch the Space and send the update again.
List Connections GET
Returns an overview of external integration connections available in the organization. Only safe, non-sensitive fields are exposed (no tokens or personal user info). Only connections the organization can use are listed. When SharePoint is switched off for the organization, its SharePoint connections are not listed, and their mappings answer 404 to a read and a write, as a connection that does not exist. Their links are kept, and return when SharePoint is switched on again. A connection belongs to a member of the organization. When that member is removed or leaves, their connection is deleted and its id answers 404 to a read and a write of its mappings. The mappings themselves are kept: list the connections again, and another member's connection to the same tenant reads and writes them under its own id. When no other member is connected, nothing is listed for that tenant until someone connects.