Skip to main content

Multi API v3.52.0

· 2 min read
Kristina Gauci

Upcoming Releases​

Breaking changes ahead of Sept/Oct 2024​

Our next breaking change release is planned to be released to Sandbox on Tuesday 24 September 2024. The release will remain on Sandbox for 3 weeks, and then we will release it to the Production environment on Tuesday 15 October 2024.

We will sendSend A transaction type that allows sending funds to another identity's instrument or to a beneficiary. Send transactions may require Strong Customer Authentication depending on the destination and whether it's a trusted beneficiary. out advance release notes in August to allow your team more time to prepare. If you have colleagues or partners who need to be in the know about Weavr release notes, ask them to subscribe to emails here.

Product Updates​

Corporate email verification endpoint now supports idempotency​

The following API endpoint can now (optionally) be called idempotently:

  • POST /corporates/verification/email/send to sendSend A transaction type that allows sending funds to another identity's instrument or to a beneficiary. Send transactions may require Strong Customer Authentication depending on the destination and whether it's a trusted beneficiary. an email verification code to the corporate root userRoot user The individual who creates the identity. For corporate identities, the root user needs to be a legal representative of the corporate such as a director or a representative who has the power of attorney over the company. For consumer identities, the root user is the owner of the identity. Every identity must always have one root user.

In this case, if the API receives a duplicate request (with the same idempotency-ref), the system will not sendSend A transaction type that allows sending funds to another identity's instrument or to a beneficiary. Send transactions may require Strong Customer Authentication depending on the destination and whether it's a trusted beneficiary. out the email multiple times.

Further information on idempotency is provided in our API Docs here.

Bulk processing capabilities - spend rules PATCH​

In the initial beta release of the Bulk ProcessBulk Process A task created when initiating a group of bulk operations. The Bulk Process has a consistent lifecycle (statuses) and management method, regardless of the type of operation being performed. It can be in states such as SUBMITTED, RUNNING, PAUSED, CANCELLED, or completed states., the ability to Update spend rules for a managed cardManaged Card A payment card (virtual or physical) that can be created and managed through the Weavr platform. Cards can operate in prepaid mode (with their own balance) or debit mode (linked to a managed account). All cards must be assigned to a card assignee who is an Authorised User. was included as an operation that can be grouped together in a bulk. This endpoint was originally created as:

POST /bulks/managed_cards/_id_/spend_rules

but has now been updated to:

PATCH /bulks/managed_cards/_id_/spend_rules

to maintain consistency with the corresponding endpoint for an individual operation.