Skip to content
RedirHub/API
Sign inGet API key
Workspace · workspace.update
POST/workspace/update/{metaKey}workspace.update

Update one workspace setting

Updates a single workspace setting, addressed by its key in the path.

Base URL
https://api.redirhub.com/v1
Auth
Bearer token
Idempotent
No
Returns
application/json

The request

Send a JSON body to POST /workspace/update/{metaKey}. value is the only required field. The metaKey path segment identifies the record.

# Update one workspace setting
curl -X POST "https://api.redirhub.com/v1/workspace/update/timezone" \
  -H "Authorization: Bearer $REDIRHUB_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "value": "string"
  }'

Path parameters

ParameterDescription
metaKeyRequiredstring

Body parameters

FieldDescription
valueRequiredstring · max 256

The response

A 200 returns the record as JSON.

{
  "id": "9f2a7c31-4b8e-4a02-9d1f-0c6b7e5a1d44",
  "name": "Acme",
  "role": "member",
  "headurl": "string",
  "personal": true,
  "country": "string",
  "pm_type": "string",
  "pm_ending": "string",
  "level": 1,
  "email": "teammate@acme.com",
  "billing_extra": "string",
  "created_at": "2026-08-01T09:14:22Z",
  "updated_at": "2026-08-01T09:14:22Z",
  "meta": [
    "string"
  ],
  "summary": [
    {
      "category": "string",
      "used": 1
    }
  ]
}

Status codes

200
SuccessThe updated workspace.
400
Bad requestThe request could not be completed.
401
UnauthenticatedUnauthenticated
422
Validation failedA field was rejected. errors lists every field with its reason.
429
Too many requestsToo many requests
484
Bad requestThe workspace role of the authenticated user is too low for this action.

What usually comes next

One call is rarely the whole job. These are the endpoints most integrations reach for around this one.