Get NFT Collection Trade Data via API

NFT market analytics have become essential for collectors, traders, and developers aiming to stay ahead in the fast-moving Web3 space. One of the most powerful tools at your disposal is the NFT trade history API, which enables real-time access to transaction data across major marketplaces. This guide dives deep into how to retrieve comprehensive NFT sales information using a robust API endpoint — perfect for building dashboards, tracking collection performance, or conducting market research.

Whether you're analyzing price trends, verifying ownership transfers, or monitoring platform-specific activity, this API delivers accurate and structured data with minimal latency.

Understanding the NFT Trade History API

The /mktplace/nft/markets/trades endpoint allows developers to fetch detailed sales records for any NFT collection across supported blockchains. You can filter results by time range, marketplace, token ID, and more — making it ideal for both broad market scans and granular investigations.

This API is part of a broader suite of Web3 APIs under Wallet-as-a-Service (WaaS) offerings, designed to streamline blockchain interactions without requiring direct node management.

👉 Discover how easy it is to integrate real-time NFT data into your app

Key Use Cases

Track floor price movements across platforms
Monitor whale transactions and bulk purchases
Audit historical trades for due diligence
Power NFT analytics dashboards or portfolio trackers
Detect wash trading or abnormal activity patterns

With support for multiple chains and integrated marketplaces, this tool ensures you’re working with up-to-date, reliable data from the most active corners of the NFT ecosystem.

Request Endpoint

GET https://web3.okx.com/api/v5/mktplace/nft/markets/trades

This RESTful endpoint returns paginated trade records in JSON format. It requires only two mandatory parameters, with several optional filters to refine your query.

Required and Optional Parameters

To make an effective request, you should understand the available parameters and how they influence the response.

Required Parameters

chain (String): The blockchain network name (e.g., ethereum, polygon). See the list of supported networks for full details.
collectionAddress (String): The smart contract address of the NFT collection you want to analyze.

Optional Filters

These parameters help narrow down the dataset:

platform (String): Filter trades by specific marketplace (e.g., OpenSea, LooksRare). Refer to integrated markets for supported values. Default: all platforms.
tokenId (String): Query trades for a specific NFT within the collection. Leave empty to include all tokens.
limit (String): Number of records per page (1–50). Defaults to 50 if not specified or out of range.
cursor (String): Pagination cursor returned from a previous response to fetch the next page.
startTime (String): Start timestamp (in milliseconds) for filtering trade history.
endTime (String): End timestamp (in milliseconds) for the query window.

Using these filters effectively can reduce bandwidth usage and improve response speed — especially when monitoring high-volume collections.

Response Structure Explained

Each API response returns a structured JSON object containing trade details and pagination metadata.

Top-Level Response Fields

cursor (String): Use this value in subsequent requests to retrieve the next set of results.
data (Array): List of individual trade objects.

Trade Object Properties

Each item in the data array includes:

amount (Integer): Number of NFTs involved in the trade (usually 1 unless bulk transfer).
chain (String): Blockchain where the transaction occurred.
collectionAddress (String): Contract address of the NFT collection.
currencyAddress (String): Token used for payment (e.g., WETH, USDC).
from (String): Seller’s wallet address.
to (String): Buyer’s wallet address.
platform (String): Marketplace facilitating the sale.
price (BigDecimal): Price per NFT in the transaction currency.
timestamp (Long): Unix timestamp (ms) of the transaction.
tokenId (String): Identifier of the traded NFT.
txHash (String): Transaction hash for on-chain verification.

This rich dataset supports advanced analysis such as price floor calculations, buyer-seller network mapping, and cross-market arbitrage detection.

Practical Request Example

Here’s how a typical API call might look:

GET https://web3.okx.com/api/v5/mktplace/nft/markets/trades?
  chain=ethereum&
  collectionAddress=0xbc4ca0eda7647a8ab7c2061c2e118a18a936f13d&
  platform=OpenSea&
  limit=10&
  startTime=1672531200000&
  endTime=1675123200000

This retrieves the 10 most recent trades on OpenSea for the Bored Ape Yacht Club (BAYC) collection during January 2023.

👉 Start pulling live NFT trade data in minutes — no infrastructure needed

Sample JSON Response

{
  "cursor": "next_page_cursor_abc123",
  "data": [
    {
      "amount": 1,
      "chain": "ethereum",
      "collectionAddress": "0xbc4ca0eda7647a8ab7c2061c2e118a18a936f13d",
      "currencyAddress": "0xc02aaa39b223fe8d0a0e5c4f27ead9083c756cc2",
      "from": "0xabc123...",
      "to": "0xdef456...",
      "platform": "OpenSea",
      "price": "95.0",
      "timestamp": 1674979200000,
      "tokenId": "8888",
      "txHash": "0x9876..."
    }
  ]
}

You can parse this data directly into analytics tools or visualize it using libraries like D3.js or Chart.js.

Frequently Asked Questions

Q: Can I use this API to track trades across multiple blockchains?
A: Yes. By changing the chain parameter, you can query trade data on any supported network, including Ethereum, Polygon, and others listed in the official documentation.

Q: Is there a rate limit for this API?
A: While specific limits depend on your access tier, standard usage allows frequent polling. For high-frequency needs, consider caching responses or using webhooks if available.

Q: How up-to-date is the trade data?
A: The system processes transactions in near real-time, typically within seconds of confirmation on-chain, ensuring timely insights.

Q: Can I filter trades by buyer or seller address?
A: Not directly through parameters, but you can filter the response data programmatically using the from and to fields.

Q: What happens if I don’t provide a cursor?
A: The API returns the latest trades first. Use the returned cursor value to paginate backward through older records.

Q: Does this include private sales or only public marketplace trades?
A: Only trades executed on integrated public marketplaces are included. Peer-to-peer transfers without marketplace involvement won’t appear unless reported by the platform.

Final Tips for Developers

To maximize efficiency:

Always use startTime and endTime when analyzing historical trends to avoid overwhelming responses.
Combine this API with metadata endpoints to enrich results with image URLs, traits, and titles.
Store cursor values temporarily to enable seamless pagination in user interfaces.

👉 See what’s possible with powerful Web3 data APIs — start building today

Core Keywords

NFT trade history API, get NFT sales data, Web3 marketplace API, fetch NFT transaction records, blockchain trade analytics, Wallet-as-a-Service API, OKX Web3 API, NFT collection analytics

By integrating this API into your workflow, you gain a strategic advantage in understanding market dynamics and making informed decisions in the evolving digital asset landscape.