# List customer Pylon issues

> Fetch Pylon issues for a customer using the search API Query params: - state: Filter by state (new, waiting_on_you, waiting_on_customer, on_hold, closed) - l...

Source: https://docs.vigilbase.com/one/api/reference/customers/get-customers-id-pylon-issues

`GET https://one.vigilbase.com/api/customers/{id}/pylon/issues`

Fetch Pylon issues for a customer using the search API Query params: - state: Filter by state (new, waiting_on_you, waiting_on_customer, on_hold, closed) - limit: Max number of issues to return (default: 50) - includeAll: If true, include closed issues (default: false)

## 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: `read:services`

## Path parameters

- `id` (string, required)

## Query parameters

- `includeAll` (string)
- `limit` (string)
- `state` (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}/pylon/issues' \
  --header "Authorization: Bearer $VIGILBASE_TOKEN"
```