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

# Versioning

> Each endpoint is versioned on its own, directly in its path.

The version sits in the path, immediately after the endpoint it belongs to:

```
POST https://api.privue.ai/pan/v1/verify
POST https://api.privue.ai/bank/v1/penny-drop
GET  https://api.privue.ai/usage/v1/summary
```

There is no suite-wide version. Each endpoint moves on its own schedule, so a new version of one
never moves another, and no migration is ever required across all of them at once.

## What a new version means

A version holds a shape steady. `pan/v1/verify` keeps taking the fields it takes today and keeps
returning the fields it returns today. Anything that would break an integration built against it
ships as `pan/v2/verify`, served alongside it.

Changes made within a version:

* adding a new optional request field
* adding a new field to a response

Treat responses as open: read the fields you need and ignore the ones you do not recognise, so a new
field never breaks your parsing.

Changes that get a new version:

* removing or renaming a field
* making an optional request field required
* changing the type or meaning of an existing field

## Related endpoints

Two endpoints that verify the same thing by different methods, such as penny drop and penny-less, are
separate endpoints rather than versions of each other, because they answer differently. They are not
interchangeable, and neither will be withdrawn in favour of the other without notice.