API referenceVirtual accounts

List virtual accounts

GET
/api/b/v1/virtual-accounts

Authorization

OAuth2PasswordBearer
AuthorizationBearer <token>

In: header

Query Parameters

currency?|null
admin_access_token?string|null

Response Body

application/json

application/json

curl -X GET "https://example.com/api/b/v1/virtual-accounts"
{  "accounts": [    {      "id": "497f6eca-6276-4993-bfeb-53cbbbba6f08",      "label": "string",      "currency": "string",      "scheme": "string",      "provider": "string",      "account_identifier": "string",      "bank_name": "string",      "routing_code": "string",      "reference_code": "string",      "status": "string",      "reference_required": true,      "created_at": "2019-08-24T14:15:22Z"    }  ]}

Everything that moved GET

One feed of every movement, newest first, paged exactly. Ordered and paged on `sequence`, a globally unique identity column, so no row is shown twice or skipped no matter what is written while somebody reads. The previous approach — merging `/charges` with `/payouts` on the client — could not offer that, because the two share no ordering. Readable by anybody who can see the business. A Viewer exists to look at the numbers, and a feed of what the business has done is the plainest form of that. 404 `NO_WALLET` when the business has no wallet: it has no book yet, which is a state to explain rather than an empty list that looks like no activity.

Open a virtual account POST

Next Page