Update details of a specific workspace
OAuth 2.1 authorization code flow with PKCE (required of every client, public or confidential). Scopes are a ceiling on the credential, not a grant of access: a token also cannot exceed what the user who approved it may already do. A write scope does not imply its matching read — ask for both.
In: header
Scope: workspaces:write
Path Parameters
Unique identifier of the workspace.
^[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}$uuidRequest Body
application/json
TypeScript Definitions
Use the request body type in TypeScript.
All fields optional. logo / icon are NOT accepted here — use the /logo and /icon endpoints.
Response Body
application/json
application/json
application/json
application/json
application/json
curl -X PUT "https://example.com/workspaces/497f6eca-6276-4993-bfeb-53cbbbba6f08" \ -H "Content-Type: application/json" \ -d '{}'{ "id": "497f6eca-6276-4993-bfeb-53cbbbba6f08", "name": "string", "slug": "string", "description": "string", "logo": "3c06f846-1ab1-40a9-8645-a19a9fdeae85", "icon": "bc9b3dc5-578a-4929-a13c-7d1a9725e2b0", "color": "string", "settings": {}, "roles": [ "string" ], "status": "active", "createdAt": 1678886400000, "updatedAt": 1678886400000}