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

# Changes to the API

> Track changes and upgrades to the Fintoc API

This page explains which API changes Fintoc treats as backwards compatible and how Fintoc versions the API when a change is not. Every change Fintoc has made to the API so far has been backwards compatible. When a change is not backwards compatible, Fintoc releases a new dated API version so your existing integration keeps working.

## Backwards compatible changes

Fintoc considers the following changes as backwards compatible:

* Add objects to the API.
* Add optional parameters to already existing API endpoints.
* Add new fields to existing objects.
* Change the order of the keys in an object.
* Change the length or format of IDs and tokens, including adding or removing prefixes such as the `acc_` prefix on the [Account object](/reference/movements-api/accounts/accounts-object) ID.
* Change header field names to uppercase or lowercase. Per [RFC 7230](https://www.rfc-editor.org/rfc/rfc7230#section-3.2), header field names are case-insensitive, while header field values are case-sensitive.

<Info>
  **You shouldn't assume the format of IDs or tokens**

  You should never *parse* an ID or a token to get information out of it. Changes to these fields are considered backwards compatible, so the format can change at any moment. For example, objects created before `2021-05-05` don't have a prefix on their IDs.
</Info>