> ## Documentation Index
> Fetch the complete documentation index at: https://docs.venlyfinance.com/llms.txt
> Use this file to discover all available pages before exploring further.

# List account supported assets

> See which assets an account can actually move, and what's blocking the rest.

**Requires scope:** `manage:accounts` — see [Required scopes](/getting-started/authentication#required-scopes-finance-api).

The same assets as [List supported assets](/api-reference/Finance-API/supported-assets/list-supported-assets), each annotated with a `permitStatus` telling you whether **this account** can move that asset yet.

Check this before offering an asset to an end-user. An asset the tenant has enabled is not automatically usable by every account: the account's wallet needs an allowance in place first, and on a self-custody wallet only the customer can grant it.

| `permitStatus`    | What it means                              | Who acts                   |
| ----------------- | ------------------------------------------ | -------------------------- |
| `READY`           | Usable now                                 | —                          |
| `ACTIVATING`      | Allowance in place, wallets not usable yet | Nobody — re-read shortly   |
| `ACTION_REQUIRED` | No allowance yet on a self-custody wallet  | **The customer** must sign |
| `PENDING`         | No allowance yet on a Venly-managed wallet | Venly                      |
| `FAILED`          | Granting the allowance failed              | Retry, then support        |
| `NO_WALLET`       | No wallet on that asset's chain            | Create one                 |

<Warning>`permitStatus` is derived on every request and never stored. Don't cache it — a status can change as soon as a customer signs or a wallet finishes activating.</Warning>

Only `READY` means "spend now". Treat everything else as unavailable, and use `ACTION_REQUIRED` as the trigger to send the customer through [permits and allowances](/guides/finance/permits-and-allowances).


## OpenAPI

````yaml api-reference/Finance-API-Specs.yaml GET /accounts/{accountId}/supported-assets
openapi: 3.1.0
info:
  title: Venly Finance API
  description: >
    REST API for the Venly Finance platform:

    - Party management (Individuals & Organisations)

    - Identity verification — hosted KYC/KYB links and Sumsub share-token
    forwarding

    - Account management with party association

    - Wallet balances & token allowances on supported chains

    - Virtual bank accounts for global pay-in (EUR SEPA, USD ACH/WIRE/RTP/SWIFT)

    - Fiat-to-crypto payment sessions (pay-in)

    - Bank pay-outs — beneficiary allow-listing, routes, and PULL/PUSH pay-outs

    - Account-to-account fiat & crypto transfers

    - EIP-2612 permits and allowances

    - Webhook registration for asynchronous event delivery


    ## Authentication


    All endpoints use OAuth2 client credentials. Obtain a token first, then
    include it in every request:


    **Step 1 — Get a token:**

    ```bash

    curl -X POST
    https://login.venly.io/auth/realms/VenlyFinance/protocol/openid-connect/token
    \
      -H "Content-Type: application/x-www-form-urlencoded" \
      -d "grant_type=client_credentials&client_id={CLIENT_ID}&client_secret={CLIENT_SECRET}"
    ```


    **Step 2 — Use the token:**

    ```

    Authorization: Bearer {access_token}

    ```


    Tokens expire after **5 minutes**. Implement refresh logic in your client.
  version: 1.5.0
  contact:
    name: Venly Support
    email: support@venly.io
    url: https://docs.venlyfinance.com
  license:
    name: Proprietary
  x-logo:
    url: https://venlyfinance.com/logo.png
  x-security-contact: security@venly.io
servers:
  - url: https://api.venlyfinance.com/v1
    description: Production
  - url: https://api-staging.venlyfinance.com/v1
    description: Staging
security:
  - OAuth2: []
tags:
  - name: Parties
    description: Party management (Individuals & Organisations)
  - name: Accounts
    description: Account management, party-role associations
  - name: Wallets
    description: Blockchain wallet balances
  - name: Virtual Bank Accounts
    description: Virtual bank account payment references for global payments
  - name: Fiat-to-crypto Payment Sessions
    description: Fiat-to-crypto payment session creation
  - name: Payout Bank Accounts
    description: Allow-listing beneficiary bank accounts as pay-out destinations
  - name: Payout Routes
    description: >-
      Account-scoped routes pairing a beneficiary bank account with a crypto
      deposit asset
  - name: Payouts
    description: Crypto-to-fiat pay-outs over a registered route
  - name: Transfers
    description: Fiat and crypto transfer operations between accounts
  - name: Permits
    description: EIP-712 permit signature management for token approvals
  - name: Supported Assets
    description: >-
      Discover which chains and assets your tenant can settle in, and whether an
      account can use them yet.
  - name: Allowances
    description: Token allowance management for wallets
  - name: Webhooks
    description: Webhook registration and delivery testing
paths:
  /accounts/{accountId}/supported-assets:
    get:
      tags:
        - Supported Assets
      summary: List an account's assets and whether it can use them
      description: >
        **Requires scope:** `manage:accounts`


        The same assets as [List supported
        assets](/api-reference/Finance-API/supported-assets/list-supported-assets),

        each annotated with a `permitStatus` telling you whether **this
        account** can move that asset

        yet.


        Check this before offering an asset to an end-user. An asset the tenant
        has enabled is not

        automatically usable by every account — the account's wallet needs an
        allowance in place

        first, and on self-custody that needs the customer to act.


        `permitStatus` is derived per request, never stored.
      operationId: listAccountSupportedAssets
      parameters:
        - $ref: '#/components/parameters/AccountId'
      responses:
        '200':
          description: The account's assets with derived usability
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/AccountSupportedAssetListResponse'
              example:
                success: true
                result:
                  - chain: BASE
                    cryptoCurrency: USDC
                    decimals: 6
                    contractAddress: '0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913'
                    permitStatus: READY
                  - chain: AVALANCHE
                    cryptoCurrency: USDC
                    decimals: 6
                    contractAddress: '0xB97EF9Ef8734C71904D8002F8b6Bc66Dd9c48a6E'
                    permitStatus: ACTION_REQUIRED
        '401':
          $ref: '#/components/responses/Unauthorized'
        '403':
          $ref: '#/components/responses/Forbidden'
        '404':
          $ref: '#/components/responses/NotFound'
        '500':
          $ref: '#/components/responses/InternalServerError'
components:
  parameters:
    AccountId:
      name: accountId
      in: path
      required: true
      description: Unique account identifier
      schema:
        type: string
        format: uuid
      example: b2a1f0e9-8c7d-4e3a-9f21-0a1b2c3d4e5f
  schemas:
    AccountSupportedAssetListResponse:
      allOf:
        - $ref: '#/components/schemas/BaseResponse'
        - type: object
          properties:
            result:
              type: array
              items:
                $ref: '#/components/schemas/AccountSupportedAsset'
    BaseResponse:
      type: object
      properties:
        success:
          type: boolean
          description: Indicates whether the request was successful
    AccountSupportedAsset:
      allOf:
        - $ref: '#/components/schemas/SupportedAsset'
        - type: object
          properties:
            permitStatus:
              $ref: '#/components/schemas/AssetPermitStatus'
    ErrorResponse:
      type: object
      description: Error response wrapper
      properties:
        success:
          type: boolean
          description: Always false for error responses
          example: false
        errors:
          type: array
          description: List of errors that occurred
          items:
            $ref: '#/components/schemas/ErrorBody'
        result:
          type: object
          nullable: true
          description: Null or omitted when success is false
    SupportedAsset:
      type: object
      description: A chain/asset pair your tenant is enabled to settle in.
      properties:
        chain:
          $ref: '#/components/schemas/BlockchainNetwork'
        cryptoCurrency:
          type: string
          description: Asset symbol
          example: USDC
        decimals:
          type: integer
          description: On-chain decimals for the asset, read from its contract
          example: 6
        contractAddress:
          type: string
          description: Token contract address on `chain`
          example: '0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913'
    AssetPermitStatus:
      type: string
      description: >
        Whether a specific account can move a specific asset right now. Derived
        per request from the

        account's wallets on that asset's chain — never stored, so re-read it
        rather than caching.


        - `READY` — usable now. The allowance is in place and the account's
        wallets are active.

        - `ACTIVATING` — the allowance is in place but the wallets are not
        usable yet. No action from
          you; re-read shortly. A stuck `ACTIVATING` is one to raise with support.
        - `ACTION_REQUIRED` — **the customer must act.** Self-custody wallets
        only: no allowance
          exists yet, and only the wallet's owner can grant it. Send them through the
          [permit or allowance flow](/guides/finance/permits-and-allowances).
        - `PENDING` — no allowance yet on a Venly-managed wallet. Venly handles
        it; no action from you.

        - `FAILED` — granting the allowance failed. Retry through the permit
        flow, or contact support.

        - `NO_WALLET` — this account has no wallet on that asset's chain, so the
        asset is unusable
          regardless of allowances.
      enum:
        - READY
        - ACTIVATING
        - ACTION_REQUIRED
        - PENDING
        - FAILED
        - NO_WALLET
    ErrorBody:
      type: object
      description: Individual error details
      properties:
        code:
          type: string
          description: Machine-readable error code
          example: invalid-request
        message:
          type: string
          description: Human-readable error message
          example: The request contains invalid parameters.
    BlockchainNetwork:
      type: string
      description: >
        Supported blockchain network. Availability per chain depends on your
        company's configured

        `supportedChains` — see [Supported chains and
        assets](/guides/finance/supported-chains-and-assets).
      enum:
        - AVALANCHE
        - BASE
        - ETHEREUM
        - POLYGON
        - SOLANA
  responses:
    Unauthorized:
      description: Authentication required or failed (401)
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/ErrorResponse'
          example:
            success: false
            errors:
              - code: unauthenticated
                message: Please authenticate to perform this action.
    Forbidden:
      description: Caller lacks the required authority/role (403)
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/ErrorResponse'
          example:
            success: false
            errors:
              - code: forbidden
                message: You do not have permission to access this resource.
    NotFound:
      description: Resource not found (404)
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/ErrorResponse'
          example:
            success: false
            errors:
              - code: account-not-found
                message: The requested resource was not found.
    InternalServerError:
      description: Unexpected server error (500)
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/ErrorResponse'
          example:
            success: false
            errors:
              - code: internal-error
                message: An unexpected error occurred. Please try again later.
  securitySchemes:
    OAuth2:
      type: oauth2
      description: >
        OAuth2 client credentials flow. Token endpoints:

        - Staging:
        https://login-staging.venly.io/auth/realms/VenlyFinance/protocol/openid-connect/token

        - Production:
        https://login.venly.io/auth/realms/VenlyFinance/protocol/openid-connect/token
      flows:
        clientCredentials:
          tokenUrl: >-
            https://login-staging.venly.io/auth/realms/VenlyFinance/protocol/openid-connect/token
          scopes: {}

````