# Refresh partner brand

> `POST /api/partners/brand/refresh`: look the partner's website brand up again (Context.dev) and store it.

Source: https://docs.vigilbase.com/one/api/reference/partners/post-partners-brand-refresh

`POST https://one.vigilbase.com/api/partners/brand/refresh`

`POST /api/partners/brand/refresh`: look the partner's website brand up again (Context.dev) and store it. Parts the partner chose stay as they are. Once per partner every 10 minutes and 3 paid lookups a day; a domain found in the last 24 hours is reused, not looked up. Staff can use it under View-as.

## 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_…`. Needs a key with write access: read-only keys get `403` with the code `read_only_key`. See [organisation API keys](https://docs.vigilbase.com/one/api#organisation-api-keys).
- Permissions checked: `admin:full`, `write:organizations`, `write:partner_services`

## Query parameters

- `impersonate_customer_id` (string)

## Body (application/json)

## Responses

### 200

Success

### 401

Authentication required

### 403

Not permitted

## Example request

```bash
# Token from `vigilbase login`, or a write API key (vb_one_…)
curl --request POST \
  --url 'https://one.vigilbase.com/api/partners/brand/refresh' \
  --header "Authorization: Bearer $VIGILBASE_TOKEN" \
  --header 'Content-Type: application/json' \
  --data '{}'
```