> ## Documentation Index > Fetch the complete documentation index at: https://docs.kirafin.ai/llms.txt > Use this file to discover all available pages before exploring further. # Get a virtual account > Retrieve a single virtual account by its UUID, including its current status and bank deposit details. The account must belong to you. On the `2026-04-14` pin, bank details are projected as flat top-level fields (`account_number`, `routing_number`, `bank_name`, `bank_address`, `account_holder_name`); the list endpoint returns `provider` and `currency` as `null`, so fetch a VA by ID when you need those fields. {/* version-stamp:start — generated by scripts/stamp-versions.ts, do not edit */} Stable since **2026-05-28** — unchanged in **2026-06-01**. {/* version-stamp:end */} ## OpenAPI ````yaml /openapi/kira-api.2026-06-01.json get /v1/virtual-accounts/{virtual_account_id} openapi: 3.1.0 info: title: Kira API version: '2026-06-01' description: >- REST API for users, KYC/KYB verification, virtual accounts, payouts, recipients, and webhooks. Every request requires an `x-api-key` header and a bearer access token (see Authentication). Pin your account to version `2026-04-14` before integrating. contact: name: Kira API Support email: support@kirafin.ai servers: - url: https://api.balampay.com description: Production - url: https://api.balampay.com/sandbox description: Sandbox security: - bearerAuth: [] apiKeyAuth: [] tags: - name: Authentication - name: Versioning - name: Users - name: Virtual Accounts - name: Quotations - name: Payouts - name: Recipients - name: Reference - name: RFIs paths: /v1/virtual-accounts/{virtual_account_id}: get: tags: - Virtual Accounts summary: Get a virtual account description: >- Retrieve a single virtual account by its UUID, including its current status and bank deposit details. The account must belong to you. On the `2026-04-14` pin, bank details are projected as flat top-level fields (`account_number`, `routing_number`, `bank_name`, `bank_address`, `account_holder_name`); the list endpoint returns `provider` and `currency` as `null`, so fetch a VA by ID when you need those fields. operationId: get_v1-virtual-accounts-virtual-account-id parameters: - in: path name: virtual_account_id required: true schema: type: string format: uuid description: Virtual account UUID. - in: header name: X-Api-Version required: false description: >- 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. schema: type: string example: '2026-06-01' responses: '200': description: Success. content: application/json: schema: $ref: '#/components/schemas/VirtualAccount' '400': description: >- Malformed id — `virtual_account_id` is not a valid UUID. Ids are format-validated **before** lookup, so a syntactically invalid id returns `400` (not `404`); `404` is reserved for well-formed ids that do not exist. content: application/json: schema: $ref: '#/components/schemas/ValidationErrorResponse' example: error: Invalid request data details: - path: id message: Invalid virtual account ID format code: invalid_string '401': description: Unauthorized. content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '404': description: Not found. content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' security: - bearerAuth: [] apiKeyAuth: [] components: schemas: VirtualAccount: type: object description: >- A virtual account as returned by the VA read endpoints (`GET /v1/virtual-accounts`, `GET /v1/virtual-accounts/{virtual_account_id}`). On the `2026-06-01` pin, `status` is the raw internal value (see the enum) and bank details are projected as flat top-level fields. The list view returns a thinner projection: `markup` is present only when fetching a single VA by ID, and `provider`/`currency` come back `null` in the list. All fields beyond the `required` set may be absent or `null`. properties: id: type: string format: uuid description: Virtual account UUID. user_id: type: string format: uuid description: UUID of the user that owns this virtual account. status: type: string enum: - pending - activating - active - failed - deactivated description: >- Raw internal account status. `active` = ready to receive deposits; `activating` = provisioning; `pending` = awaiting KYC; `failed` = creation failed; `deactivated` = closed. Poll until `active` before use. On the `2026-06-01` pin the raw enum is returned (the KYB mapping applied on `2026-04-14` was reverted at `2026-05-28`). type: type: string enum: - US_BANK description: Virtual account type. bank: type: - string - 'null' description: Selected bank/provider rail (e.g. `slovak_savings_bank` in sandbox). mode: type: string enum: - fiat - crypto description: Funding mode. Fixed at creation. destination: type: - object - 'null' description: >- Crypto payout destination (`currency`, `network`, `address`). `null` for fiat-mode accounts. additionalProperties: true source_deposit_instructions: type: - object - 'null' description: >- Provider deposit instructions the flat bank fields are projected from. additionalProperties: true payment_methods: type: - object - 'null' description: Inbound/outbound payment methods supported by this account. properties: inbound: type: - array - 'null' items: $ref: '#/components/schemas/PaymentMethod' description: >- Inbound (deposit) payment methods this account supports. Array of `{name, status}` (see `PaymentMethod`), e.g. `[{name: "WIRE", status: "active"}, {name: "ACH", status: "active"}, {name: "WALLET", status: "active"}]` on a crypto virtual account. `status` is one of `active`, `coming-soon`, `disabled`. outbound: type: - array - 'null' items: $ref: '#/components/schemas/PaymentMethod' description: >- Outbound (payout) payment methods this account supports. Array of `{name, status}`, e.g. `[{name: "WIRE", status: "active"}, {name: "ACH", status: "coming-soon"}]` on a crypto virtual account. `status` is one of `active`, `coming-soon`, `disabled`. methods: type: - object - 'null' description: Alias of `payment_methods` (same shape). properties: inbound: type: - array - 'null' items: $ref: '#/components/schemas/PaymentMethod' description: >- Alias of `payment_methods.inbound` — byte-identical value on the same VA fetch. outbound: type: - array - 'null' items: $ref: '#/components/schemas/PaymentMethod' description: >- Alias of `payment_methods.outbound` — byte-identical value on the same VA fetch. account_holder_name: type: - string - 'null' description: Flat bank detail projected from `source_deposit_instructions`. account_number: type: - string - 'null' description: >- Flat bank detail. `null` (or the ACT-only `"PENDING-ACT-ACCOUNT"` sentinel) until the account is provisioned. routing_number: type: - string - 'null' description: Flat bank detail projected from `source_deposit_instructions`. bank_name: type: - string - 'null' description: Flat bank detail projected from `source_deposit_instructions`. bank_address: type: - string - 'null' description: Flat bank detail projected from `source_deposit_instructions`. account_holder_address: type: - string - 'null' description: Flat bank detail projected from `source_deposit_instructions`. description: type: string description: Human-readable label set at creation. status_reason: type: string description: Human-readable reason backing the current status (e.g. RFI details). markup: type: object description: >- Markup configuration. Present only when fetching a single VA by ID — omitted from the list projection. additionalProperties: true created_at: type: string description: ISO 8601 timestamp. updated_at: type: string description: ISO 8601 timestamp. metadata: type: object description: Customer-attached Stripe-style key/value metadata. additionalProperties: true required: - id - user_id - status - type - mode - created_at - updated_at ValidationErrorResponse: type: object description: >- Validation / request error. The body shape is **not uniform** across the API — it varies by endpoint and by which validation layer rejects the request. The fields below are the union of what may appear; treat them all as optional. Observed shapes include `{ code, message }`, `{ code, message, errors[] }`, `{ code, error, details[] }`, `{ error, details[] }`, and a nested `{ error: { code, message, details } }`. Always branch on the HTTP status, not on a fixed body shape. properties: code: type: string message: type: string error: type: - string - object description: >- A short error label (e.g. `"Invalid data"`), or on some endpoints a nested `{ code, message, details }` object. errors: type: array items: type: object properties: field: type: string message: type: string required: - field - message details: type: - array - object description: >- Per-issue detail. Shape varies by endpoint — typically an array of `{ message }` or `{ path, message, code }`, occasionally an object. ErrorResponse: type: object properties: message: type: string code: type: string statusCode: type: number error: type: string timestamp: type: string path: type: string details: {} required: - message PaymentMethod: type: object description: A single supported payment method on a virtual account. properties: name: type: string description: Method name (e.g. `WIRE`, `ACH`). status: type: string description: Method status (e.g. `active`). required: - name - status securitySchemes: bearerAuth: type: http scheme: bearer bearerFormat: JWT description: Access token from `POST /auth` (the `data.access_token` value). apiKeyAuth: type: apiKey in: header name: x-api-key description: API key issued by Kira. Required on every request, including `/auth`. ````