Planned Backwards Compatibility Changes
  • Updated on 07 Jul 2020
  • 2 minutes to read
  • Print
  • Share
  • Dark
    Light

Planned Backwards Compatibility Changes

  • Print
  • Share
  • Dark
    Light

Overview

Change Reference ID Backwards compatible until
Apply Read permission standards on API 1.0 GET transaction channels endpoint ADM-1958 18th September 2020
Apply Read permission standards on API 1.0 GET roles endpoint IAM-815 18th September 2020
Replacing Default Sort Criterion 'lastModifiedDate' with 'creationDate' for Paginated Lists via API 2.0 across Mambu DEP-1580; CORE-2721; CUS-2438; CUS-2445 31st September 2020

Apply Read permission standards on API 1.0 GET transaction channels endpoint

With the introduction of Granular Administrator Permissions Standards via V9.48 and V9.49, you can now only access and use transaction channels via Mambu UI and Mambu API 2.0, only if you have specific permissions to your user account or you have a user type Administrator.

As the design of API 1.0 does not support adding this new behaviour on top, we would like to let you know that we will be requesting View permission in order to access GET /api/transactionchannels API 1.0 endpoint in the week of 18th of September.

This gives you 3 months to prepare the transition to this new behaviour and ensure none of your integration relies on access without standard permission authorisation to these endpoints.

Apply Read permission standards on API 1.0 GET roles endpoint

With the introduction of Granular Administrator Permissions Standards via V9.48 and V9.49, you can now only access and use roles via Mambu UI and Mambu API 2.0, only if you have specific permissions to your user account or you have a user type Administrator.

As the design of API 1.0 does not support adding this new behaviour on top, we would like to let you know that we will be requesting View permission in order to access GET /api/userroles and GET /api/userroles/{encodedKey} API 1.0 endpoint in the week of 18th of September.

This gives you 3 months to prepare the transition to this new behaviour and ensure none of your integration relies on access without standard permission authorisation to these endpoints.

Replacing Default Sort Criterion 'lastModifiedDate' with 'creationDate' for Paginated Lists via API 2.0 across Mambu

When retrieving paginated lists of clients, deposit or loan accounts via API 2.0, Mambu might return the pages with missing and duplicate entries. By default the retrieved lists are currently sorted by “lastModifiedDate”, which is a mutable field. Between two API calls (to retrieve different pages of the same list), some accounts or clients could be modified and therefore they would change order in the retrieved pages. In certain integrations relying solely on an entity's position in the list, this could lead to missing entries and duplicates.

To create predictable and consistent lists, we are redesigning our API 2.0 GET endpoints to sort retrieved lists across Mambu by “creationDate” - an immutable field. This change affects the following endpoints:

  • GET /api/deposits (DEP-1580)
  • GET /api/loans (CORE-2721)
  • GET /api/clients (CUS-2438)
  • GET /api/groups (CUS-2445)
Was this article helpful?