Accounts

Use GET /v1/accounts to discover your authorized Accounts. Use GET /v1/accounts/{ccv} to retrieve one. Both endpoints return the same Account representation.

The Profile mapped to your credential must have a current, active, confirmed Account Relation with consultation permission. Accounts in PRE_OPENING and DISABLED remain visible when that permission permits consultation.

{
  "ccv": "00321203110000000031",
  "name": null,
  "status": "ACTIVE",
  "omnibus": false,
  "capabilities": ["WALLET_BALANCE_READ", "ORDER_CREATE", "ORDER_CANCEL"],
  "observedAt": "2026-09-21T10:11:12.123456Z"
}

Every response includes all schema fields, including fields set to null. name may be null or blank, and capabilities may be empty. The API does not return Account IDs, bank details, other users, or internal organization and accounting data.

Stable Account selection

A CCV is a 20-digit identifier with valid control digits. Once exposed, it is immutable and never reused.

A malformed or checksum-invalid CCV returns 422 validation-failed with a /ccv violation. Valid unknown and inaccessible CCVs return the same 404 not-found. Permission changes take effect on each read.

Informational capabilities

Capability	Required Account permission	Account status
WALLET_BALANCE_READ	Balance consultation	Any
ORDER_CREATE	Order creation	ACTIVE
ORDER_CANCEL	Order cancellation	ACTIVE

Capabilities always appear in the order above. The API calculates them from the current relation permissions and Account state. It checks authorization again when a command runs and may apply other business validation, so a capability does not guarantee success. The response has no consultation capability because consultation permission is required to see the Account.

List Accounts

Results use ascending CCV order. Account discovery has no filters. See Pagination for page size, response metadata and cursor continuation.

Every Account on a page has the same observedAt. The API creates a new timestamp for each later page. Empty pages do not include an observation timestamp.

Request failures

The list endpoint rejects a blank limit, repeated parameters and unknown parameters with 400 invalid-request. Common page-size and cursor failures are described in Pagination.

The detail endpoint accepts no query parameters. If the service cannot read an Account required for the response, it returns 503 service-unavailable rather than omit that Account. See Errors for the common problem contract.