# List Vigil conversation approvals

> GET /api/vigil/conversations/{conversationId}/approvals on the Vigilbase One API.

Source: https://docs.vigilbase.com/one/api/reference/vigil/get-vigil-conversations-conversation-id-approvals

`GET https://one.vigilbase.com/api/vigil/conversations/{conversationId}/approvals`

## Authorizations

- `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`. Organisation API keys can't call this endpoint: it acts for a signed-in person or changes how people sign in.
- Permissions checked: `approve:vigil-actions`, `write:deployments`, `write:services`

## Path parameters

- `conversationId` (string, required)

## Responses

### 200

Success

### 401

Authentication required

### 403

Not permitted

## Example request

```bash
# Token from `vigilbase login`. API keys can't call this.
curl --request GET \
  --url 'https://one.vigilbase.com/api/vigil/conversations/{conversationId}/approvals' \
  --header "Authorization: Bearer $VIGILBASE_TOKEN"
```