# List SCIM tokens

> Source: https://elaichi.ai/docs/api-reference/scim-tokens/scim-token/listscimtokens/

`GET /scim-token`

Resource: **Scim Token** · API: **SCIM tokens**

## Response body

- **`result`** _(array<object>)_
  - **`id`** _(string)_
    SCIM token id.
  - **`organization_id`** _(string)_
    Organization (`org_…`) it provisions into.
  - **`user_id`** _(string)_
    User (`usr_…`) who minted it.
  - **`name`** _(string)_
  - **`last_used_at`** _(string,null)_
  - **`impersonated_by_user_id`** _(string,null)_
    Set when Elaichi support created this token while signed in as `user_id` (a support session). The token keeps working after the support session ends, but is refused with `403 staff_impersonation_blocked` once the organization turns `allow_staff_impersonation` off, and its actions are audited with `metadata.impersonated_by_user_id`. `null` for a token the member created themselves.
  - **`created_at`** _(string)_
  - **`updated_at`** _(string)_
- **`next_cursor`** _(string,null)_
- **`prev_cursor`** _(string,null)_

## Code examples

### curl

```bash
curl -X GET 'https://api.elaichi.ai/scim-token' \
  -H 'Authorization: Bearer $ELAICHI_API_TOKEN' \
  -H 'Content-Type: application/json'
```

### JavaScript

```javascript
const response = await fetch('https://api.elaichi.ai/scim-token', {
  method: 'GET',
  headers: {
    'Authorization': 'Bearer ' + process.env.ELAICHI_API_TOKEN,
    'Content-Type': 'application/json',
  },
});

const data = await response.json();
console.log(data);
```

### Python

```python
import os
import requests

url = "https://api.elaichi.ai/scim-token"
headers = {
    "Authorization": f"Bearer {os.environ['ELAICHI_API_TOKEN']}",
    "Content-Type": "application/json",
}

response = requests.get(url, headers=headers)
print(response.json())
```