List virtual accounts
Use limit<=100 — limit above 100 returns a clean 400 validation error (same cap as GET /v1/users; applies to ALL list endpoints). There is no top-level provider or currency on a virtual account — the rail is exposed as bank, and a crypto VA’s currency is under destination.currency (identical in list and get-by-id views).
Status filter vs. response status: the status query filter uses the raw lifecycle values (pending, activating, active, failed, deactivated), while the status on each returned account is the KYB-mapped value (approved, rfi, declined, deactivated). Filter on raw; read the mapped value off the response.
Authorizations
Access token from POST /auth (the data.access_token value).
API key issued by Kira. Required on every request, including /auth.
Headers
Optional. The date-versioned API version to apply for this request (e.g. 2026-04-14). When sent it always wins, even over your pinned account default. When omitted, the API uses your account's pinned version if set, otherwise a baseline default.
"2026-04-14"
Query Parameters
Maximum number of virtual accounts to return (1-100).
1 <= x <= 100Number of virtual accounts to skip for pagination.
x >= 0Filter by raw account status (not the KYB-mapped value shown on the response).
pending, activating, active, failed, deactivated Filter by owning user UUID.
Filter by virtual account type.
US_BANK Filter by funding mode.
fiat, crypto Free-text search (1-255 characters).
1 - 255Stripe-style metadata filter — ?metadata[key]=value deep-object form. Each key must be 1-40 characters and must not contain [ or ]. Multiple keys are AND-ed.