Get Asset for an Address Using Runes API

·

Accessing blockchain-based digital assets has become increasingly seamless thanks to advanced Web3 APIs. One powerful tool in this space is the Runes API, part of the broader WaaS (Wallet-as-a-Service) Web3 API suite, which enables developers and platforms to retrieve detailed information about rune assets associated with specific wallet addresses. This guide dives into how you can use the Get Owned Assets endpoint effectively, understand its parameters, interpret responses, and integrate it into your decentralized applications.

Whether you're building a marketplace, analytics dashboard, or asset tracker, understanding how to pull accurate rune ownership data is essential. Let’s explore the technical structure and practical applications of this API.


🔧 API Endpoint Overview

The Get Owned Assets API allows you to fetch all rune assets held by one or more wallet addresses on supported blockchains. It's particularly useful for platforms that need real-time visibility into user-held digital collectibles or fungible tokens based on the Runes protocol.

Request URL

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

This endpoint supports batch queries, meaning you can request data for up to 20 wallet addresses at once—ideal for performance optimization in user-facing apps.


📥 Request Parameters

To make a successful call, include the following parameters:

ParameterTypeRequiredDescription
runesIdStringYesUnique identifier for the rune token
walletAddressesStringYesComma-separated list of wallet addresses (max 20)
cursorStringNoPagination cursor (points to next set; max 1,000 records)
limitIntegerNoNumber of results per page (default: 10, max: 100)
✅ Tip: Use limit=100 and manage pagination via cursor to efficiently handle large datasets without overwhelming your server.

👉 Discover how to automate asset tracking across multiple wallets effortlessly.


📤 Response Parameters

The API returns a comprehensive JSON response detailing each asset. Here’s what each field means:

This rich dataset empowers developers to build dynamic UIs showing balances, prices, listing statuses, and visual icons—all from a single API call.


💬 Practical Use Cases

1. NFT Marketplace Integration

Marketplaces can use this API to verify ownership before allowing listings or trades. By checking the status and ownerAddress, platforms ensure only legitimate holders can list assets.

2. Portfolio Trackers

Aggregators tracking user assets across chains can batch-fetch rune holdings using comma-separated addresses, then display real-time valuations in BTC and USD.

3. Wallet Applications

Self-custody wallets can enhance user experience by automatically detecting and displaying runes without requiring manual token imports.

👉 See how top-tier Web3 platforms streamline asset discovery with automated syncing.


🔍 Sample Request & Response

While full JSON examples aren’t included here due to formatting constraints, a typical flow looks like this:

Sample Request:

GET /api/v5/mktplace/nft/runes/get-owned-assets?runesId=rune-123&walletAddresses=bc1qabc...,bc1qxyz...&limit=50

Expected Behavior:

You can parse the response to extract:


❓ Frequently Asked Questions

Q: Can I query more than 20 wallet addresses in one request?

No. The maximum number of wallet addresses per request is capped at 20. To process more, split them into multiple requests and aggregate results server-side.

Q: What does "unavailable: 1" mean in the response?

It indicates the UTXO contains multiple Atomicals assets, making it incompatible with standard transfers or listings due to potential conflicts.

Q: How often is the price data updated?

Pricing (in BTC, USD, sats) reflects real-time marketplace listings and is updated as new orders are placed or filled. However, unlisted assets will have null or zero price values.

Q: Is there rate limiting on this API?

Yes. For stability and fair usage, high-frequency requests may be throttled. Implement caching and exponential backoff strategies in production environments.

Q: Does this support testnet or only mainnet?

Currently, the Runes API operates on mainnet only. Always verify chain IDs before processing transactions.


🔑 Core Keywords

To align with search intent and improve SEO visibility, key phrases naturally integrated throughout this article include:

These terms reflect common queries from developers and businesses exploring blockchain integration.


🚀 Final Thoughts

The Get Owned Assets endpoint is a cornerstone for any application interacting with Runes-based digital assets. With support for batch queries, detailed metadata, and real-time pricing, it simplifies what would otherwise require complex on-chain parsing.

As the Runes ecosystem grows, tools like this will become increasingly vital for enabling transparency, liquidity, and usability in decentralized finance and digital ownership.

👉 Start integrating powerful Web3 features today—explore seamless blockchain access now.