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

# Balance

> Retrieves the token balance for a specific wallet address on the blockchain. To use this endpoint, you'll need the `token-address` that was returned by the [createAndMintToken](/omni-platform/omniomni-components/omni-safe/create-tokens) endpoint when the token was initially created. This `token-address` acts as an identifier within OmniSafe for the specific token you are querying. The `owner` parameter specifies the *wallet address* for which you want to retrieve the token balance.



## OpenAPI

````yaml GET /v1/tokens/{token-address}/{owner}
openapi: 3.0.1
info:
  contact:
    email: developers@ecrop.com
    name: ecrop OmniSafe API Support
    url: https://ecrop.de/contact/
  description: >
    # Preparation Guide

    Welcome to the OmniSafe API Documentation. This document provides a detailed
    list of available APIs and methods for managing wallets, tokens, and
    transfers. Before beginning your integration, it’s recommended to review the
    following essential documents:

    - **API Service Guide (Essential, Pro):** Designed for non-technical users,
      this guide helps in selecting the best API package based on business needs.
      Review it [here](https://youki.atlassian.net/wiki/spaces/mar/pages/534183949/API+Service+Guide).  # Keep or adapt

    - **Integration Handbook:** Targeted at developers, this handbook includes
      crucial details such as endpoint URLs, authentication methods,
      request/response formats, and error handling. It is essential for
      successful integration. Access the handbooks here:

      - [🌳 Pro Package Integration Handbook] # Keep or adapt

      - [🌱 Essential Package Integration Handbook] # Keep or adapt

    Familiarizing yourself with these documents will ensure a smoother
    integration process.
  license:
    name: ecrop OmniSafe
    url: https://developers.ecrop.de/api-license/
  termsOfService: https://developers.ecrop.de/terms-of-use/
  title: OmniSafe API Catalogue
  version: 1.0.0
  x-logo:
    backgroundColor: '#DDDDDD'
    url: >-
      https://static.wixstatic.com/media/fd3e8b_a57864adb1084dea94c9fab462a8f52c~mv2.png/v1/crop/x_0,y_131,w_1253,h_295/fill/w_233,h_55,al_c,q_85,usm_0.66_1.00_0.01,enc_auto/fd3e8b_a57864adb1084dea94c9fab462a8f52c~mv2.png
servers:
  - description: Default
    url: https://omnisafe.sandbox.ecrop.de/omni-safe
security:
  - Bearer Authentication: []
tags:
  - name: Wallets
    description: Endpoints for managing wallets
  - name: Tokens
    description: Endpoints for managing tokens
  - name: Transfers
    description: Endpoints for managing transfers
paths:
  /v1/tokens/{token-address}/{owner}:
    get:
      tags:
        - Tokens
      summary: Get balance
      description: >-
        Retrieves the token balance for a specific wallet address on the
        blockchain. To use this endpoint, you'll need the `token-address` that
        was returned by the
        [createAndMintToken](/omni-platform/omniomni-components/omni-safe/create-tokens)
        endpoint when the token was initially created. This `token-address` acts
        as an identifier within OmniSafe for the specific token you are
        querying. The `owner` parameter specifies the *wallet address* for which
        you want to retrieve the token balance.
      operationId: balanceOf
      parameters:
        - name: token-address
          in: path
          required: true
          schema:
            type: string
          description: The address of the token, ETH for Ethereum.
        - name: owner
          in: path
          required: true
          schema:
            type: string
            description: The address of the owner.
      responses:
        '200':
          description: Wallet balance
          content:
            application/json:
              schema:
                type: number
components:
  securitySchemes:
    Bearer Authentication:
      type: http
      scheme: bearer
      bearerFormat: JWT

````