In the rapidly evolving world of Web3 and decentralized marketplaces, accessing real-time data on active offers for NFTs is essential for developers, traders, and platform builders. The Query Offer endpoint provided by OKX's Marketplace API enables seamless retrieval of active offers on specific NFTs within the Seaport contract ecosystem. Whether you're building a marketplace dashboard, analyzing bidding trends, or integrating NFT trading functionality into your dApp, this API delivers structured, reliable, and scalable data.
This guide dives deep into how to use the GET /api/v5/mktplace/nft/markets/offers endpoint effectively, covering request parameters, response structure, sorting options, and practical implementation tips — all while aligning with SEO best practices and user search intent.
Understanding the Query Offer Endpoint
The Query Offer endpoint allows you to retrieve a list of active (and optionally filtered) offers placed on a particular NFT or across an entire collection. It operates under the Seaport protocol — one of the most widely adopted standards for decentralized NFT trading on Ethereum and EVM-compatible chains.
👉 Discover how to integrate real-time NFT offer data into your dApp today.
This makes it ideal for use cases such as:
- Monitoring bid activity on rare digital assets
- Powering analytics tools for NFT collectors
- Enabling instant price discovery in secondary markets
- Supporting automated offer acceptance systems
By leveraging this API, developers gain access to granular order-level details including price, currency, expiration time, and wallet-level metadata — all delivered through a secure, low-latency interface.
Request Details
Endpoint URL
GET https://web3.okx.com/api/v5/mktplace/nft/markets/offersThis RESTful endpoint supports standard HTTPS queries and returns JSON-formatted responses suitable for server-side and client-side integrations.
Supported Request Parameters
You can customize your query using the following optional and required parameters:
| Parameter | Type | Required | Description |
|---|---|---|---|
chain | String | Yes | Name of the blockchain (e.g., ETH, Polygon, BSC). See supported blockchains for full list. |
collectionAddress | String | No | Contract address of the NFT collection. |
tokenId | String | No | Unique identifier of the NFT within its collection. |
maker | String | No | Filter results by the wallet address that created the offer. |
createAfter | String | No | Only return offers created after this Unix timestamp (in seconds). |
createBefore | String | No | Only return offers created before this Unix timestamp. |
updateAfter | String | No | Return offers updated after this timestamp. |
updateBefore | String | No | Return offers updated before this timestamp. |
status | String | No | Filter by order status: active, inactive, cancelled, or sold. |
sort | String | No | Sort results by: create_time_desc, update_time_desc, price_desc, or price_asc. Default is ascending creation time. |
limit | String | No | Number of records per page (default: 50, maximum may vary). |
cursor | String | No | Pagination cursor for retrieving subsequent pages of results. |
🔍 Pro Tip: To fetch all active bids on a specific NFT, combinechain,collectionAddress,tokenId, and setstatus=active.
Response Structure
The API returns an array of order objects conforming to the OKX Order Model, each containing detailed metadata about the offer.
Key response fields include:
- orderId: Unique identifier for the order.
- createTime / updateTime: Timestamps (in milliseconds) indicating when the order was created or last modified.
- listingTime / expirationTime: When the offer became active and when it expires.
- status: Current state of the offer (
active,cancelled, etc.). - orderHash: Cryptographic hash of the order, useful for verification.
- protocolData: Full JSON payload of the Seaport order parameters.
- protocolAddress: Address of the Seaport contract fulfilling the trade.
- chain: Blockchain network where the offer exists.
- maker: Wallet address that placed the offer.
- orderType: Will be
"Offer"for bid-type orders. - price: Price per NFT in base units (e.g., wei).
- currencyAddress: Token used to make the offer (e.g., WETH, USDC).
- collectionAddress / tokenId: Identifies the targeted NFT.
- amount: Quantity of NFTs covered by the offer (usually 1 for ERC-721).
Practical Use Case: Tracking High-Value Offers
Imagine you're developing a watchlist tool for Blue-Chip NFT collections like CryptoPunks or Bored Ape Yacht Club. Using this API, you could:
- Set
chain=ETHand specify the collection contract. - Query every hour with
updateAfter=[last check timestamp]. - Sort by
price_descto surface the highest bids. - Alert users if a new top offer exceeds a threshold.
This empowers collectors and investors to react quickly to market movements — turning raw blockchain data into actionable intelligence.
👉 Learn how to build powerful NFT monitoring tools with live offer tracking.
Core Keywords for SEO Optimization
To ensure visibility and relevance in search engines, the following core keywords have been naturally integrated throughout this article:
- NFT offers API
- Seaport contract offers
- fetch active NFT bids
- Web3 marketplace API
- OKX Order API
- NFT bid tracking
- blockchain offer query
- decentralized marketplace data
These terms reflect high-intent searches from developers and product teams looking to integrate real-time bid data into their platforms.
Frequently Asked Questions (FAQ)
Q: Can I use this API to get offers for multiple NFTs at once?
A: While you cannot query multiple token IDs in a single request, you can omit tokenId to retrieve offers across an entire collection, then filter client-side.
Q: Is there a rate limit for this endpoint?
A: Yes, typical rate limits apply based on your API key tier. For high-frequency access, consider caching responses or using webhooks if available.
Q: How up-to-date is the offer data?
A: Data is refreshed in near real-time. Most updates appear within seconds of blockchain confirmation.
Q: What does "orderType: Offer" mean?
A: It indicates a bid placed by a buyer — i.e., an offer to purchase an NFT at a specified price.
Q: Can I retrieve expired or cancelled offers?
A: Yes, by setting status=cancelled or filtering manually using expirationTime.
Q: Does this work with both ERC-721 and ERC-1155 tokens?
A: Yes, the endpoint supports both standards as long as they are traded via the Seaport protocol.
Best Practices for Integration
- Use Pagination Wisely: Always capture and reuse the
cursorvalue to navigate large datasets efficiently. - Filter Early: Apply
chain,collectionAddress, andstatusfilters server-side to reduce payload size. - Handle Timezones Correctly: Convert Unix timestamps (
createAfter, etc.) accurately using UTC to avoid mismatches. - Validate Order Integrity: Use
orderHashandprotocolDatato verify offers off-chain before processing. - Monitor Expiry Times: Regularly check
expirationTimeto avoid acting on stale bids.
👉 Start integrating live NFT offer data into your application now — fast, reliable, scalable.
With robust filtering, flexible sorting, and comprehensive response data, the Query Offer endpoint is a cornerstone for any Web3 application requiring accurate insight into NFT bidding activity. Whether you're building analytics dashboards, alert systems, or full-fledged marketplaces, this API provides the foundation you need.
By combining developer-friendly design with enterprise-grade reliability, OKX empowers builders to create next-generation experiences in the decentralized digital economy.