Skip to content

API reference

Get branding

workspace.GetBrandingReadAPI key

Read the workspace's display name, registered name, primary domain, logo, icon and company profile.

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

Access & visibility

Allow workspace.GetBranding 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

No parameters. Send an empty JSON object ({}).

Response

Returns 200 OK with a JSON body.

These are the workspace's branding assets and profile, not a customer's Company record. Asset URLs are public presentation assets; do not upload confidential images as branding.

namestringRequired

Display name.

registered_namestringRequired

Registered legal name of the organization.

domainstring or nullRequired

Website hostname, without a scheme or path.

icon_urlstring or nullRequired

URL of the workspace's configured icon.

logo_urlstring or nullRequired

URL of the workspace's configured logo.

profile_mdstring or nullRequired

Workspace company profile formatted as Markdown.

Errors & retries

This operation reads data. It needs no idempotency key and can be retried after a transient failure.

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.
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.

Next steps

Download OpenAPI · Versioning & retirement

JSON schemas

Use the complete schemas for validation or client generation.

Full request JSON schema
{
  "type": "object",
  "properties": {},
  "additionalProperties": false,
  "examples": [
    {}
  ]
}
Full response JSON schema
{
  "type": "object",
  "properties": {
    "name": {
      "type": "string",
      "description": "Display name."
    },
    "registered_name": {
      "type": "string",
      "description": "Registered legal name of the organization."
    },
    "domain": {
      "type": [
        "string",
        "null"
      ],
      "description": "Website hostname, without a scheme or path."
    },
    "icon_url": {
      "type": [
        "string",
        "null"
      ],
      "description": "URL of the workspace's configured icon."
    },
    "logo_url": {
      "type": [
        "string",
        "null"
      ],
      "description": "URL of the workspace's configured logo."
    },
    "profile_md": {
      "type": [
        "string",
        "null"
      ],
      "description": "Workspace company profile formatted as Markdown."
    }
  },
  "required": [
    "name",
    "registered_name",
    "domain",
    "icon_url",
    "logo_url",
    "profile_md"
  ],
  "additionalProperties": false,
  "examples": [
    {
      "name": "Example project",
      "registered_name": "Northstar Consulting AS",
      "domain": null,
      "icon_url": "https://example.com/icon.png",
      "logo_url": "https://example.com/logo.svg",
      "profile_md": "Northstar helps small businesses organize their customer work."
    }
  ]
}

Search by operation name or what you want to build.

Use arrow keys to browse. Enter opens a result.