Retrieve Wallet Assets Using Runes API

·

This guide explains how to fetch Runes-based assets for a wallet address via the OKX Web3 API.


API Overview

The get-owned-asserts endpoint retrieves Runes token holdings for specified wallet addresses.

Key Features


API Request

Endpoint

GET https://web3.okx.com/api/v5/mktplace/nft/runes/get-owned-asserts

Required Parameters

ParameterTypeRequiredDescription
runesIdStringYesUnique token identifier
walletAddressesStringYesComma-separated addresses (max 20)

Optional Parameters

ParameterTypeDefaultDescription
cursorString-Pagination cursor (max 1000 records)
limitInteger10Results per page (max 100)

👉 Explore Web3 API use cases


Response Format

Successful responses include these key fields:

FieldTypeDescription
tickerStringToken name (e.g., "RUNE-A")
amountStringToken quantity in UTXO
usdPriceBigDecimalCurrent USD valuation
statusIntegerListing status (0=unlisted)

Sample Response Snippet

{
  "assetId": "x7f8...",
  "ticker": "RUNE-A",
  "amount": "1500",
  "usdPrice": 24.50,
  "chain": 1
}

Implementation Notes

  1. Rate Limits: 10 requests/second
  2. Error Handling: Check unavailable flag for UTXO conflicts
  3. Data Freshness: confirmations field shows blockchain sync status

👉 Get API rate limit tips


FAQ

How many wallets can I query per request?

The API supports up to 20 comma-separated addresses in a single call.

What chain networks are supported?

Currently supports Bitcoin mainnet (chain=1) with Ethereum compatibility coming Q3 2024.

Why are some assets marked 'unavailable'?

This indicates UTXO conflicts - typically when one transaction contains multiple token types.

How do I paginate through large result sets?

Use the cursor parameter from the last record of each response batch.

Is historical price data available?

Not via this endpoint - use the OHLCV API for time-series data.

Can I filter by token type?

Yes - set tickerType=4 to retrieve only Runes tokens.


---

### Key SEO Elements Integrated:
- **Primary Keywords**: Runes API, wallet assets, Web3 API  
- **Secondary Keywords**: UTXO, pagination, blockchain sync  
- **Anchor Texts**: Contextual links to OKX with engagement triggers  
- **Structure**: Hierarchical headings with parameter tables  
- **Length**: Expanded with implementation notes and FAQ