Skip to content

API reference

Update workspace profile

workspace.UpdateWorkspaceProfileWriteAPI key

Update the workspace's name, language, billing email or primary domain. Claiming a domain requires human approval and cannot use a public email-provider domain.

POST/v1/operations/workspace.UpdateWorkspaceProfile
On this page

Access & visibility

Allow workspace.UpdateWorkspaceProfile on your API key.

Workspace access by default. Private member data requires approved member delegation through Brigg-Act-As; the key supplies permissions while private ownership and project boundaries remain enforced.

Set up authentication · Choose permissions

Request fields

Send a JSON object with the following fields. Required fields must be included; omit optional fields you do not need.

namestringOptional

Display name.

At least 1 character. At most 80 characters.

brand_namestring or "" or nullOptional

The trading name customers know the company by; empty or null clears it, and every customer-facing surface then shows name.

default_languagestringOptional

Default language of the workspace.

Allowed: "no", "en", "sv", "da".

invoice_emailstring or "" or nullOptional

Empty string or null clears it.

domainstring or "" or nullOptional

The PRIMARY/branding domain — a bare host; empty or null clears it. Must not be a public webmail host or a domain another workspace claims.

Response

Returns 200 OK with a JSON body.

okbooleanRequired

Whether the action completed successfully.

Errors & retries

Set BRIGG_REQUEST_ID once for each logical action. The samples send it as Idempotency-Key. Reuse the same value and body on retries, including after a timeout; a missing response does not prove the action failed.

For rate limits, follow the server’s retry guidance and back off. See HTTP errors and safe retries and limits.

HTTP status Code What to do
400 invalid_json Send a JSON object with Content-Type: application/json.
400 invalid_input Check the request fields and types. Supply a stable Idempotency-Key containing 1–200 characters.
401 invalid_key The workspace API key is missing, invalid or revoked.
403 forbidden Check the key’s operation and resource grants. If Brigg-Act-As is supplied, the key must be authorized to delegate to that member.
404 not_found The requested operation or resource is not available to this credential.
429 rate_limited Wait for Retry-After before retrying. Reuse the original Idempotency-Key.

Next steps

Download OpenAPI · Versioning & retirement

JSON schemas

Use the complete schemas for validation or client generation.

Full request JSON schema
{
  "type": "object",
  "properties": {
    "name": {
      "type": "string",
      "minLength": 1,
      "maxLength": 80,
      "description": "Display name."
    },
    "brand_name": {
      "anyOf": [
        {
          "type": "string",
          "maxLength": 80
        },
        {
          "type": "string",
          "const": ""
        },
        {
          "type": "null"
        }
      ],
      "description": "The trading name customers know the company by; empty or null clears it, and every customer-facing surface then shows `name`."
    },
    "default_language": {
      "type": "string",
      "enum": [
        "no",
        "en",
        "sv",
        "da"
      ],
      "description": "Default language of the workspace."
    },
    "invoice_email": {
      "anyOf": [
        {
          "type": "string",
          "format": "email"
        },
        {
          "type": "string",
          "const": ""
        },
        {
          "type": "null"
        }
      ],
      "description": "Empty string or null clears it."
    },
    "domain": {
      "anyOf": [
        {
          "type": "string",
          "maxLength": 253
        },
        {
          "type": "string",
          "const": ""
        },
        {
          "type": "null"
        }
      ],
      "description": "The PRIMARY/branding domain — a bare host; empty or null clears it. Must not be a public webmail host or a domain another workspace claims."
    }
  },
  "additionalProperties": false,
  "examples": [
    {}
  ]
}
Full response JSON schema
{
  "type": "object",
  "properties": {
    "ok": {
      "type": "boolean",
      "description": "Whether the action completed successfully."
    }
  },
  "required": [
    "ok"
  ],
  "additionalProperties": false,
  "examples": [
    {
      "ok": true
    }
  ]
}

Search by operation name or what you want to build.

Use arrow keys to browse. Enter opens a result.