Introducing the new Weavr Multi v3 API
Over the last few months, we have been working hard to improve the Weavr Multi API. Your feedback has been instrumental in this, and we are excited to launch the new version - the Weavr Multi API v3. This new version is not only simpler, but will also better cater to your growing needs.
You can have a look at the new API docs and accompanying guides here.
Defining the API using RESTful guidelines
V3 embraces the OpenAPI specification and uses different HTTP methods to represent CRUD (Create, Read, Update, Delete) operations. You can use publicly available code generators to reduce repetitive work.
Decoupling IBANs from Accounts
Managed accounts may, or may not, have IBANs - you and your customers choose what works best. Managed accounts represent pots of funds and can be used to segregate money based on your customers’ needs.
This will help your customers have more control over their funds, and help improve reconciliation. An IBAN can be optionally assigned to a managed account via the API whenever required.
Consumer identities now support multiple users
We have generalised the concept of authorised users, which was previously only supported for Corporate identities. Now, Consumer identities can also invite users to their account.
This new feature unlocks a whole new range of models, as Consumers can now share their account with another user or family member. One example of this in practice, is a parent/ child linked account. In this instance, a parent can extend a card or account to their child while keeping control of how and where it is being used.
Get Started
You can start using the new Weavr Multi v3 API, today. Your Sandbox API Keys will work with both versions of the API.
We will continue to support the current version of the API, so you can rest assured that there will be no disruption to service. However, we do encourage you to have a look at the new version, along with the features we have launched, and will be launching in the coming months.
Eventually, the Weavr Multi v2 API will be phased out. However, we will give you plenty of advance notice before this happens, and will be on hand to support you along the way. We will communicate the process and deprecation dates, in future updates.