# List your Vigil conversations

> Every Vigil conversation the signed-in operator started, company chats and chats about customers together (`GET /api/vigil/conversations/mine`).

Source: https://docs.vigilbase.com/one/api/reference/vigil/get-vigil-conversations-mine

`GET https://one.vigilbase.com/api/vigil/conversations/mine`

Every Vigil conversation the signed-in operator started, company chats and chats about customers together (`GET /api/vigil/conversations/mine`). Used by the iOS chat list so conversations begun on a customer page on the web are listed too. Vigilbase operators only: authorized as a company-scope request, so customers (who have one scope already) get 404.

## 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.

## Query parameters

- `limit` (integer): Default `20`. Minimum 1, maximum 50.
- `offset` (integer): Default `0`. Minimum 0, maximum 10000.
- `q` (string): Max length 200.

## 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/mine' \
  --header "Authorization: Bearer $VIGILBASE_TOKEN"
```