# Get tool run brand

> `GET /api/tool-runs/:id/brand`: the brand a saved run's PDF is exported under.

Source: https://docs.vigilbase.com/one/api/reference/tool-runs/get-tool-runs-id-brand

`GET https://one.vigilbase.com/api/tool-runs/{id}/brand`

`GET /api/tool-runs/:id/brand`: the brand a saved run's PDF is exported under. A run of a customer a partner manages is partner-branded (name, colour, same-origin logo path); anything else is Vigilbase's.

## Authorizations

Send one of these:

- `Authorization` (string, header, required): Bearer access token from Vigilbase Identity (`auth.vigilbase.com`), sent as `Authorization: Bearer <token>`. The CLI gets one with `vigilbase login`.
- `Authorization` (string, header, required): Organisation API key (`vb_one_…`) from **Settings → API keys** in Vigilbase One, sent as `Authorization: Bearer vb_one_…`. Read-only keys work. See [organisation API keys](https://docs.vigilbase.com/one/api#organisation-api-keys).

## Path parameters

- `id` (string, required)

## Query parameters

- `customerId` (string)

## Responses

### 200

Success

### 401

Authentication required

### 403

Not permitted

## Example request

```bash
# Token from `vigilbase login`, or an API key (vb_one_…)
curl --request GET \
  --url 'https://one.vigilbase.com/api/tool-runs/{id}/brand' \
  --header "Authorization: Bearer $VIGILBASE_TOKEN"
```