In the rapidly evolving world of blockchain and digital assets, Runes have emerged as a unique class of tokenized assets built on the Bitcoin network. As demand grows for seamless trading experiences, leveraging APIs to automate and streamline operations becomes essential. This guide walks you through how to submit a Rune listing using the OKX Web3 API, part of the broader Wallet-as-a-Service (WaaS) and marketplace solutions designed for developers and businesses building in the Web3 space.
Whether you're managing digital collectibles, tokenized assets, or decentralized finance (DeFi) tools, understanding how to programmatically list Runes empowers you to scale your operations efficiently.
How to Submit a Rune Listing
The "Submit a Rune Listing" API endpoint allows developers to list a single Rune inscription directly onto the OKX marketplace. Before initiating a listing, it’s recommended to first retrieve your wallet's asset holdings using the Get Wallet Assets API to identify which Runes are available for listing.
This integration is ideal for platforms aiming to offer automated listing capabilities, NFT marketplaces expanding into Bitcoin-native tokens, or developers building Rune management dashboards.
👉 Discover how easy it is to integrate powerful Web3 tools with OKX’s developer-friendly API suite.
Endpoint
POST https://web3.okx.com/api/v5/mktplace/nft/runes/make-order
This secure POST request requires authentication and structured payload data to successfully process a listing on the OKX platform.
Request Parameters
To ensure successful execution, include the following parameters in your API call:
runesId(String, required)
The unique identifier for the Rune token. Example:840000:3walletAddress(String, required)
The Bitcoin wallet address holding the specified Rune inscription.utxo(String, required)
The Unspent Transaction Output (UTXO) where the Rune resides. Format:txHash:vout.
Example:d578a0967605257f75be625cbdc2506f2a52f9135f56f302badab6a3da54e0d4:0unitPrice(BigDecimal, required)
The price per unit of the Rune, denominated in satoshis (sats) — the smallest fraction of a BTC.totalPrice(BigDecimal, required)
The total listing price in BTC, representing the full value of the inscription being listed.psbt(String, required)
A fully signed Partially Signed Bitcoin Transaction (PSBT), provided in base64 encoding.
Important constraints:- The UTXO containing the Rune must be placed at input index
1. - The output with the payment address and amount must be located at output index
1.
- The UTXO containing the Rune must be placed at input index
These requirements ensure compatibility with OKX’s transaction validation logic and prevent processing errors.
Response Parameters
After submitting your request, OKX returns a standardized JSON response:
code(Integer)
Indicates success or failure. A value of0means success; any other value signals an error.data(Object)
Contains detailed response data upon success (e.g., order ID, status). Structure varies based on operation outcome.msg(String)
A human-readable message explaining the result. Especially useful whencode ≠ 0, providing insight into what went wrong.
Example Request
{
"runesId": "840000:3",
"walletAddress": "bc1qxyz...",
"utxo": "d578a0967605257f75be625cbdc2506f2a52f9135f56f302badab6a3da54e0d4:0",
"unitPrice": "100000",
"totalPrice": "0.01",
"psbt": "cHNidP8BAJoC..."
}This example submits a listing for a specific Rune at 100,000 sats per unit, totaling 0.01 BTC.
Example Response (Success)
{
"code": 0,
"data": {
"orderId": "ORD20250415123456789",
"status": "listed",
"listedAt": "2025-04-15T12:34:56Z"
},
"msg": "Order placed successfully"
}A successful response confirms that the listing has been published on the marketplace and includes metadata such as the order ID and timestamp.
Example Response (Error)
{
"code": 4001,
"msg": "Invalid PSBT: UTXO not found at input index 1"
}Error responses help debug issues related to formatting, authentication, or transaction structure.
Core Keywords
For optimal SEO and discoverability, this article integrates the following keywords naturally throughout the content:
- Rune listing API
- Submit Runes order
- Web3 marketplace API
- Bitcoin NFT API
- Wallet-as-a-Service (WaaS)
- OKX Runes integration
- Programmatic NFT listing
- Blockchain asset management
These terms align with common search queries from developers and businesses exploring automated Rune trading solutions.
Frequently Asked Questions
What is a Rune listing?
A Rune listing refers to placing a Bitcoin-based Rune token for sale on a digital marketplace. Runes are fungible tokens inscribed directly on Bitcoin’s blockchain using ordinal theory, similar to NFTs but with distinct economic models.
Why does the PSBT need specific input/output indexing?
OKX enforces strict PSBT formatting to standardize transaction parsing and ensure security. Placing the Rune UTXO at input index 1 and payment details at output index 1 allows consistent automation across thousands of listings.
Can I list multiple Runes at once?
Currently, this API supports only single-Rune listings per request. To list multiple items, batch your calls with appropriate delays to avoid rate limiting.
👉 Automate your digital asset workflows with high-performance Web3 APIs built for scalability.
Is there a fee to list Runes?
Listing itself is typically free on OKX; however, blockchain transaction fees apply when transferring or selling Runes. Ensure sufficient BTC balance in your wallet to cover network costs.
How do I check if my listing was successful?
Monitor the code field in the response. If code = 0, your listing is live. You can also use OKX’s order query APIs to retrieve real-time status updates.
Do I need KYC verification to use this API?
Yes, access to certain WaaS features—including marketplace operations—may require identity verification depending on your region and usage level. Check OKX’s developer portal for compliance requirements.
Best Practices for Developers
- Always validate UTXO ownership before crafting PSBTs.
- Use test environments to simulate transactions before going live.
- Implement retry logic with exponential backoff for failed requests.
- Store order IDs securely for future reference or cancellation.
- Monitor API rate limits to maintain performance during high-volume operations.
By following these guidelines, you enhance reliability and reduce downtime in production applications.
Ready to bring automation to your Runes trading strategy? With OKX’s robust Web3 infrastructure, developers can build powerful tools that interact seamlessly with Bitcoin’s growing ecosystem of tokenized assets.
👉 Start building today with OKX’s comprehensive Web3 API suite — fast, secure, and developer-first.