Get Runes Collection: Comprehensive Guide to Runes API and Marketplace Integration

Introduction

The Runes API provides developers and collectors with detailed insights into Runes collections, including holder statistics, transaction data, and market metrics. This guide explores the API's functionality, request parameters, and response structure to help you integrate Runes data seamlessly into your Web3 applications.

API Overview

This API retrieves Runes metadata such as:

Holder count
Collection links
Transaction volume (BTC/USD)
Sales activity
Floor price metrics

👉 Explore the Runes Marketplace for real-time data and trends.

Request Specifications

Endpoint

GET https://web3.okx.com/api/v5/mktplace/nft/runes/detail

Parameters

Parameter	Type	Required	Description
`runesId`	String	Yes	Comma-separated Runes IDs (e.g., `840000:3,840000:28`)

Response Structure

Field	Type	Description
`runesId`	String	Unique Rune identifier
`name`	String	Rune name
`spacename`	String	Dotted notation of the name
`maxMintNumber`	String	Maximum mintable units
`mintedNumber`	String	Already minted units
`limitPerMint`	String	Minting limit per transaction
`deployedTime`	Long	Timestamp of deployment
`symbol`	String	Token symbol
`floorprice`	String	Floor price (Sats)
`holders`	Integer	Total holders

👉 Optimize your app with WaaS Web3 APIs.

Use Cases

Market Analysis: Track totalVolume and marketCap for investment decisions.
Collection Management: Use collectionUrl to link to OKX listings.
Minting Strategies: Analyze limitPerMint and mintedNumber for supply insights.

FAQs

How do I query multiple Runes?

Provide comma-separated IDs in the runesId parameter (e.g., 840000:3,840000:28).

What units are used for pricing?

floorprice: Sats (1 BTC = 100,000,000 Sats)
usdFloorPrice: USD equivalent

Is historical data available?

Yes, deployedTime and block ranges (startBlock/endBlock) provide temporal context.

Best Practices

Batch Queries: Reduce API calls by querying multiple Runes simultaneously.
Error Handling: Validate runesId formatting to avoid incomplete responses.
Data Caching: Store frequently accessed metrics (e.g., holders) locally to minimize latency.

For advanced integration, refer to the 👉 OKX API documentation.

Note: All financial metrics (e.g., usdTotalVolume) are derived from real-time market data.


### Key SEO Keywords:  
1. Runes API  
2. NFT Marketplace  
3. Web3 Integration  
4. Floor Price  
5. Blockchain Analytics  
6. OKX Collections  
7. WaaS API