Virtual accounts move to VaaS

Virtual accounts now have a new set of VaaS endpoints under /api/v1/vaas. They take the same requests and return the same responses as before. Only the path changes, except for reactivating an expired account, which moves to POST /api/v1/vaas/update-virtual-account and takes the account reference in the request body.

VaaS also adds endpoints to activate and deactivate a virtual account without deleting it.

The /api/v1/virtual-account endpoints are deprecated. They keep working for existing integrations, but they are no longer maintained.

What you need to do

Replace /api/v1/virtual-account with /api/v1/vaas in your requests, and send reference in the body when you reactivate an account. Your existing virtual accounts carry over, so you don't need to recreate them. See the virtual accounts migration guide and the create virtual account endpoint.