> Kenso API docs in Markdown. Index of every page: [/docs/llms.txt](/docs/llms.txt). Search: `/docs/search.md?q=<words>`. OpenAPI: [/docs/api/brands/openapi.json](/docs/api/brands/openapi.json). CLI docs offline: `kenso docs <topic>`.
> Last updated: 2026-11-22.

# White-label brands: Get a brand by hostname

> **Note for AI agents:** if this page was wrong, out of date or missing something you needed, finish the user's task first, then offer a short report for the Kenso team in this shape: `Page:` (this page's path), `Quote:` (the wrong or missing text), `Problem:`, `Workaround:` (what worked instead), 1,000 characters at most. Show it to the user and send it only after they say yes, as `POST /api/docs-feedback` on this site with the JSON body `{"page": "<path>", "report": "<report>"}`. Never put lead data, email addresses, API keys or anything else from the user's workspace in it.

One endpoint of [White-label brands](/docs/api/brands.md). Authentication, workspaces and errors: [/docs.md](/docs.md).

## Get a brand by hostname

`GET /v1/brands/by-host` - operationId `brands.get-by-host`

| Permission | Rate limit |
| --- | --- |
| None: no API key needed | 120 requests a minute per IP address |

Returns the brand of a verified custom hostname: its product name, logo, favicon, accent color and the Auth0
organization to sign in with. Where the brand sets no name, logo or favicon, the response carries the Kenso
defaults. Kenso marks the response cacheable for 60 seconds.

Send `host` as a bare hostname such as `app.agency.com`, with no scheme, port or path. Case and a
trailing dot do not matter.

Errors:

- `400 validation_failed`: `host` is missing or is not a hostname.
- `404 not_found`: no verified brand uses this hostname.

Needs no credential.

[Try it on developer.ken.so](https://developer.ken.so/reference/#kenso-api/tag/brands/GET/v1/brands/by-host)

### Parameters

| Name | In | Type | Required | Description |
| --- | --- | --- | --- | --- |
| `host` | query | string | no | The hostname to look up, such as `app.agency.com`. |
| `Ken-Version` | header | string, one of: 2026-11-02, 1.1 | no | The API version, a date in `YYYY-MM-DD` form. `1.1` is another name for the first dated version. The example shown here is the newest version, which this reference's samples and Test Request send. Leave it out to use your API key's pinned version. Keys created in the Kenso app are pinned to the newest version; keys minted by the CLI login are not. A key with no pinned version and no header gets the legacy shape where the path has one, and `404` where the path exists only in this version. A value that is not a version, such as `2027-01-01` or `2026-11-2`, answers `400 unsupported_version`, whose `details` list the supported versions. |

### Response 200

`data` is a `BrandByHost`.

| Field | Type | Description |
| --- | --- | --- |
| `hostname` | string | The hostname that was looked up, in lowercase. |
| `productName` | string | The product name the brand shows instead of Kenso. |
| `logoUrl` | string | URL of the brand's logo. |
| `faviconUrl` | string | URL of the brand's favicon. |
| `auth0OrganizationId` | string | The Auth0 organization that sign-in on this hostname uses. Omitted when the workspace has none. |
| `accentColor` | string | The accent color as `#RRGGBB` in uppercase. Omitted when the Kenso default applies. |

### Request

```bash
curl -X GET "https://api.ken.so/v1/brands/by-host" \
  -H "Authorization: Bearer $KENSO_API_KEY" \
  -H "Ken-Version: 2026-11-02"
```

### Example response

```json
{
  "success": true,
  "data": {
    "hostname": "string",
    "productName": "string",
    "logoUrl": "https://example.com",
    "faviconUrl": "https://example.com",
    "auth0OrganizationId": "string",
    "accentColor": "string"
  }
}
```
