Naar inhoud springen
Tibata
Docs
Spaces

Update Space

PATCH
/v1/spaces/{space_id}

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.

Autorisatie

bearerAuth
headerAutorisatieBearer <token>

Padparameters

space_id*string

ID of the Space

Request-body

Space fields to update

application/json
  1. body
name?string

Name of the space

slug?string

URL-friendly identifier for the space, unique within the organization

Patroon^[a-z0-9]+(?:-[a-z0-9]+)*$
description?string

Short description of the space

Responsbody

Space updated

application/json
  1. response
data*
Voorbeeldverzoek
curl -X PATCH 'https://api.tibata.ai/v1/spaces/string' \  -H 'Content-Type: application/json' \  -d '{}'
Voorbeeldrespons
{  "data": {    "id": "string",    "name": "string",    "slug": "string",    "description": "string",    "url": "http://example.com",    "restricted": true  }}