Changes to the API

The IF Platform API exposes multiple workflows to handle different use cases with connections on a single concept. Some of the high-level changes we will be required to do over time are workflow additions, workflow customisation changes and adding connections. These high-level changes might cause some data structures to change (additions of new fields, some fields becoming optional or required etc…).

This guide is here to help you build your integration with the IF Platform in a way that ensures that it will remain functional no matter what releases occur thereafter.

1. Versioning & Breaking Changes

We will not release any breaking changes to any API. If we need to completely redesign and change the structure of an API, then instead we will release a new version of the API.

2. Container Objects

We have implemented the container objects into our API to ensure we have enough flexibility while we are releasing major changes to the API without affecting existing integrations.

Container objects allow us to add new workflows/connections to a particular operation with completely different input or output data structures. We use the workflow container object as an example to explain the concept, but the same principles apply to other container objects as well.

For instance, if you are using the "direct" workflow to create clients, you will not be affected by the addition of the "migration" workflow for the same operation. This is the result of having a completely different input data structure, as the data structures are evaluated based on the workflow code supplied to the API.

Container objects also allow us to add new customization to a particular workflow without breaking the existing usage of that workflow. By adding new "optional" fields to the workflow container object, where there were previously no values corresponding to the behaviour before the addition of that field, we can add new customization where existing integrations continue working as expected at the same time providing the capability to use the new customization when required.

3. Additions and Removal of Fields

01/11/2021

• Added phone to client profile. Clients
• Added contact object including phone and email to beneficiary object. Beneficiaries
  Note: address object has been moved into contact object but the create api will still continue to work as expected, i.e. it is a backward-compatible change. We would always notify you in case of breaking changes.
• Added schemeAttributes map for currency and payment scheme specific attributes to outgoing transfer object. Outgoing Transfers

12/08/2022

• Added a new endpoint for querying service provider specific transfer reasons: Outgoing Transfers
  GET /accounts/{accountId}/transfer-reasons/{{country}}
• GET /transfer-reasons/{{country}} - This endpoint will be DEPRECATED soon. We'll be supporting both endpoints for a while. We recommend using the new endpoint for getting transfer reasons.