Utilities

Get asset metadata

Changed on

Authenticated asset lookup. GET accepts required ids and fields as comma-separated or repeated query parameters; at most 100 IDs before deduplication. Supported fields: name, symbol, decimals, price, logo. QUERY /assets is also supported (not representable as an OpenAPI 3.1 operation): send application/json {"ids":["eip155:1:native"],"fields":["symbol","price"]}, at most 100 IDs and a 64 KiB body. Both methods return exact submitted ID keys, omit unrequested fields and use null for unresolved requested fields; item errors remain HTTP 200. An invalid request returns 400 with {"error":{"code":"invalid_request","message":"..."}}.

get/assets

Request

Query parameters

idsstring required

Required comma-separated asset IDs (or repeated ids); at most 100 submitted IDs

Example:eip155:1:native
fieldsstring required

Required comma-separated fields (or repeated fields): name,symbol,decimals,price,logo

Example:symbol,price

Headers

x-api-keystring

API key for authentication

Example:your-api-key

Response

Requested asset fields keyed by exact submitted ID

dataobject required

Changes

    • info

      the endpoint scheme security internalProjectBearer was added to the API

    • info

      the endpoint scheme security tenantApiKey was added to the API

    • info

      the header request parameter x-api-key became optional

    • info

      added the non-success response with the status

    • info

      added the non-success response with the status

    • info

      endpoint added