> ## Documentation Index
> Fetch the complete documentation index at: https://docs.bey.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# API Versioning

> How Beyond Presence REST API endpoints are versioned and how to pin the version your integration uses.

All Beyond Presence API endpoints are versioned. The version is the first segment of every endpoint path:

```sh theme={null}
curl "https://api.bey.dev/{version}/{endpoint}"
```

For example, the following request calls version 1 of the [List Avatars](/api-reference/avatars/list-avatars) endpoint:

```sh theme={null}
curl "https://api.bey.dev/v1/avatars" \
  --header 'x-api-key: sk-your-api-key-here'
```

## Supported Versions

| Version | Base URL | Status |
| - | - | - |
| `v1` | `https://api.bey.dev/v1/` | Current |

The interface of a version stays stable once released. We may add new endpoints, optional request parameters, and response fields to an existing version, so make sure your client ignores fields it does not recognize. Changes that could break existing integrations, such as removing or renaming endpoints or fields, are only ever introduced through a new version or a new endpoint, and the previous one remains available as described in our [Deprecation Policy](/concepts/api/deprecation).


## Related topics

- [API Errors](/concepts/api/errors.md)
- [Verify API Key](/api-reference/authentication/verify-api-key.md)
- [API Deprecation Policy](/concepts/api/deprecation.md)
- [Beyond Presence REST API](/concepts/api/index.md)
- [List External API Configurations](/api-reference/agents-external-apis/list-external-api-configurations.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.