The digital asset landscape continues to evolve, and Runes—fungible tokens built on the Bitcoin blockchain—are gaining momentum among developers, collectors, and investors. Whether you're building a Web3 application, analyzing market trends, or managing a digital portfolio, accessing accurate and real-time data is essential. The Runes API and Marketplace API offered through OKX’s Web3 infrastructure provide powerful tools to retrieve comprehensive information about Runes collections.
This guide dives deep into how to use the Get Runes Collection endpoint to retrieve key metrics such as holder count, floor price, transaction volume, market cap, and more. We’ll walk through request parameters, response fields, and practical use cases—all while optimizing your understanding for both technical integration and strategic decision-making.
Understanding the Runes API Endpoint
The primary function of this API is to fetch detailed data about specific Runes tokens. It supports single or batch queries, making it ideal for applications that need to display or analyze multiple Runes at once.
Endpoint Overview
🔹 HTTP Method: GET
🔹 Request URL: https://web3.okx.com/api/v5/mktplace/nft/runes/detail
This endpoint returns structured JSON data containing all relevant metadata and market performance indicators for the requested Runes.
Request Parameters
To query the API effectively, you must include the required parameter in your request:
| Parameter | Type | Required | Description |
|---|---|---|---|
runesId | String | Yes | Unique identifier(s) for the Rune(s). Supports batch queries using comma-separated values (e.g., 840000:3,840000:28) |
👉 Access real-time Runes data using advanced Web3 APIs today.
For example:
GET https://web3.okx.com/api/v5/mktplace/nft/runes/detail?runesId=840000:3,840000:28This allows developers to pull data for multiple Runes in a single HTTP call, reducing latency and improving efficiency—especially useful for dashboards or analytics platforms.
Response Parameters Explained
The API returns a rich set of fields that offer insights into both technical specifications and market dynamics of each Rune. Here's what each response field means:
runesId: The unique identifier of the Rune.name: Official name of the token.spacename: Human-readable name with dot notation (e.g., "Test•Token").maxMintNumber: Maximum supply cap for the Rune.mintedNumber: Number of tokens already minted.limitPerMint: Maximum amount one address can mint per transaction.deployedTime: Timestamp (in milliseconds) when the Rune was deployed.startBlock/endBlock: Block range during which minting is allowed.symbol: Ticker symbol (e.g., "TT").divisibility: Number of decimal places supported (precision level).collectionUrl: Direct link to view the collection on OKX’s NFT marketplace.totalVolume: Total trading volume in BTC.usdTotalVolume: Same volume converted to USD.marketCap: Market capitalization in BTC.usdMarketCap: Market cap in USD.floorprice: Lowest listed price in Satoshis (Sats).usdFloorPrice: Floor price in USD.holders: Total number of unique wallet addresses holding the token.salesCount: Total number of completed sales transactions.
These metrics are crucial for assessing scarcity, demand, liquidity, and community engagement—key factors in evaluating digital asset value.
Practical Use Cases
1. Portfolio Tracking Applications
Developers can integrate this API into portfolio trackers to display live stats for users’ Runes holdings, including floor price changes and volume trends.
2. Market Analysis Dashboards
Analysts can aggregate data across multiple Runes to identify emerging trends, compare minting activity, or monitor holder growth over time.
3. NFT Marketplace Integrations
Platforms listing Runes can use the collectionUrl and floor price data to drive traffic and ensure accurate pricing displays.
4. On-Chain Research Tools
Researchers studying Bitcoin-based token standards can leverage minting limits, deployment times, and divisibility settings to understand protocol behavior.
Frequently Asked Questions (FAQ)
Q: Can I query more than two Runes at once?
A: Yes. The API supports batch queries with up to dozens of runesId values separated by commas. Just ensure your total request length stays within standard URL limits.
Q: Is there a rate limit for this API?
A: While specific thresholds may vary, it's recommended to implement throttling in your application to avoid excessive requests. For high-frequency access, consider using WebSocket streams if available.
Q: What does "floor price in Sats" mean?
A: Since Runes operate on Bitcoin’s blockchain, prices are often denominated in Satoshis (the smallest unit of BTC). 1 BTC = 100,000,000 Sats.
Q: How often is the market data updated?
A: Data is refreshed in near real-time based on blockchain events and exchange activity. Delays should typically be under a minute.
Q: Can I get historical price data from this endpoint?
A: No. This endpoint provides current snapshot data only. For time-series analysis, you'll need to store responses periodically or access a dedicated historical API.
👉 Unlock advanced blockchain analytics with powerful Web3 development tools.
Core Keywords for SEO Optimization
To enhance visibility and align with user search intent, the following core keywords have been naturally integrated throughout this article:
- Runes collection
- Runes API
- Marketplace API
- Web3 API Docs
- Bitcoin fungible tokens
- NFT marketplace API
- on-chain data API
- digital asset analytics
These terms reflect common queries from developers, investors, and researchers exploring Runes ecosystems.
Best Practices for Integration
- Validate Input: Always sanitize and validate
runesIdinputs before sending requests. - Handle Errors Gracefully: Implement proper error handling for cases like invalid IDs or service outages.
- Cache Responses: To reduce load and improve speed, cache results for frequently accessed Runes.
- Monitor Changes: Track updates to deployment times, mint limits, or floor prices for alerts or notifications.
- Secure Your Calls: If used client-side, consider proxying through your backend to protect against abuse.
Final Thoughts
As Bitcoin-based token standards like Runes gain traction, having reliable access to accurate on-chain and market data becomes increasingly valuable. The Runes API from OKX empowers developers and analysts with structured, real-time insights into token supply, holder distribution, trading volume, and pricing—all critical components for informed decision-making in Web3.
Whether you're building the next generation of decentralized applications or conducting deep market research, leveraging robust APIs like this one ensures you stay ahead in a fast-moving ecosystem.
👉 Start building with scalable Web3 APIs trusted by developers worldwide.