# List customer partner deals

> Deal amounts and their aggregates are billing data (read:billing or admin:full).

Source: https://docs.vigilbase.com/one/api/reference/customers/get-customers-id-partner-deals

`GET https://one.vigilbase.com/api/customers/{id}/partner-deals`

Deal amounts and their aggregates are billing data (read:billing or admin:full). One exception: a partner sees the values of the deals it registered itself under read:partner_deals, per deal; other deals on its pipeline stay hidden. Internal staff who reach this route through read:customers, and a partner looking at another partner it manages, get the pipeline without amounts.

## 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).
- Permissions checked: `admin:full`, `read:customers`, `read:partner_deals`

## Path parameters

- `id` (string, required)

## Query parameters

- `pipelineId` (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/customers/{id}/partner-deals' \
  --header "Authorization: Bearer $VIGILBASE_TOKEN"
```