# Get details of a specific token

Returns detailed information about the specified token asset.

Endpoint: GET /tokens/{chain_gid}/{asset_path}
Version: 1.0.0
Security: ApiKeyAuth

## Path parameters:

  - `chain_gid` (string, required)
    Blockchain identifier in CAIP-2 format (namespace:reference)
    Example: "eip155:1"

  - `asset_path` (string, required)
    Asset type identifier in CAIP-19 format (asset_namespace:asset_reference)
    Example: "erc20:0x6B175474E89094C44Da98b954EedeAC495271d0F"

## Response 200 fields (application/json):

  - `gid` (string, required)
    Asset identifier in CAIP-19 format. Identifies a asset across blockchains.
Format: /:
Examples: - Ethereum ETH: eip155:1/slip44:60 - Ethereum USDT ERC-20: eip155:1/erc20:0xdAC17F958D2ee523a2206206994597C13D831ec7
    Example: "eip155:1/erc20:0xdAC17F958D2ee523a2206206994597C13D831ec7"

  - `decimals` (integer, required)
    Number of decimal places for the token (e.g., 6 for USDT, 18 for ETH)
    Example: 6

  - `name` (string, required)
    Full token name (e.g., "Tether USD", "Ethereum", "Binance Coin")
    Example: "Tether USD"

  - `symbol` (string, required)
    Token symbol (e.g., "USDT", "ETH", "BNB")
    Example: "USDT"

  - `created_at` (string, required)
    Timestamp when the resource was created
    Example: "2024-01-15T10:30:00Z"

## Response 400 fields (application/problem+json):

  - `type` (string, required)
    A URI reference that identifies the problem type
    Example: "https://docs.vilna.io/apis/problems/invalid-request"

  - `title` (string, required)
    A short, human-readable summary of the problem type
    Example: "Invalid Request"

  - `status` (integer, required)
    The HTTP status code
    Example: 400

  - `detail` (string)
    A human-readable explanation specific to this occurrence of the problem
    Example: "Validation error"

  - `instance` (string)
    A URI reference that identifies the specific occurrence of the problem
    Example: "/errors?id=XXXXXX-xxxxx"

  - `fields` (array)
    List of invalid fields in the request

  - `fields.name` (string, required)
    The name of the invalid field
    Example: "meta"

  - `fields.reason` (string, required)
    Why this field is invalid
    Example: "Exceeded maximum data size — must not exceed 1000 characters"

## Response 404 fields (application/problem+json):

  - `type` (string, required)
    A URI reference that identifies the problem type
    Example: "https://docs.vilna.io/apis/problems/not-found"

  - `title` (string, required)
    A short, human-readable summary of the problem type
    Example: "Not Found"

  - `status` (integer, required)
    The HTTP status code
    Example: 404

  - `detail` (string)
    A human-readable explanation specific to this occurrence of the problem
    Example: "The requested resource was not found"

  - `instance` (string)
    A URI reference that identifies the specific occurrence of the problem
    Example: "/errors?id=XXXXXX-xxxxx"

## Response default fields (application/problem+json):

  - `detail` (string)
    A human-readable explanation specific to this occurrence of the problem
    Example: "An unexpected error occurred while processing your request"

  - `instance` (string)
    A URI reference that identifies the specific occurrence of the problem
    Example: "/errors/1234567890"

  - `status` (integer, required)
    The HTTP status code
    Example: 500

  - `title` (string, required)
    A short, human-readable summary of the problem type
    Example: "Internal Server Error"

  - `type` (string, required)
    A URI reference that identifies the problem type
    Example: "https://api.vilna.io/problems/internal-error"