Changes to the API

Track changes and upgrades to the Fintoc API

Up until now, every change to the Fintoc API has been backwards compatible. Whenever we make a change that is not backwards compatible, we will release a new version of the API to prevent your code from breaking.

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 the IDs and tokens. This includes adding or removing prefixes (like the acc_ prefix on the ID of the Account Object).
  • Change header's field names to uppercase or lowercase. According to RFC7230, header field names are case-insensitive. Note that field values are case-sensitive.


You shouldn't assume the format of IDs nor 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.

API Changelog


  • The pending field was added to the Movement Object to denote movements that could still be reverted by the bank.
  • The status field was added to the Link Object that indicates whether it is necessary for the user to reconnect the Link or not.


  • The object field was added to every object returned by the API. That way, whenever you get a response body from the API, you can know the object type from the object field.

  • A prefix was added to every ID from the API. That way, whenever you see an ID you can know to which object type it corresponds.


What about old IDs?

Old IDs don't change, you can expect to continue seeing them like before the change. Only objects created after 2021-05-05 have the new ID format.







  • The sender_account, recipient_account and comment fields were added to the Movement Object.