Fractal Ordinals are redefining how digital assets are created, traded, and tracked on the Bitcoin blockchain. As interest in Bitcoin-based NFTs and BRC-20 tokens grows, accessing accurate and timely transaction data becomes essential for developers, traders, and Web3 platforms. The Fractal Ordinals API enables seamless retrieval of comprehensive trade history across major marketplaces, empowering users with real-time insights into NFT and token activities.
This guide explores how to use the Retrieve Fractal Ordinals Activities endpoint to fetch detailed transaction records, including buyer and seller addresses, pricing data, timestamps, and more. Whether you're building a marketplace analytics dashboard or tracking wallet activity, this API delivers structured, sortable, and filterable data optimized for integration.
Understanding the Fractal Ordinals Trade History Endpoint
The /nft/fractal-ordinals/trade-history endpoint returns all transaction records associated with a specific collection. Each record includes granular details such as:
- Transaction origin (
fromAddress) and destination (toAddress) - Timestamp of the trade
- Price denominated in Fractional Bitcoin (FB)
- Unit price and quantity
- Transaction type (e.g., SALE, LIST, TRANSFER)
- Source platform (e.g., OKX, Magic Eden)
By default, results are sorted in descending order by transaction time—ensuring the most recent trades appear first—making it ideal for monitoring live market movements.
👉 Access real-time Fractal Ordinals data using powerful Web3 APIs today.
Request Parameters: Customize Your Data Output
You can fine-tune your request using optional parameters to support pagination, filtering, and sorting.
Required Parameter
slug(String): The unique identifier (slug) of the NFT collection. This is required to specify which collection’s transaction history you want to retrieve.
Optional Filters
cursor(String): Used for pagination. Pass a cursor value to fetch the next set of results.limit(String): Controls the number of records returned per call. Defaults to 10; maximum allowed is 100.sort(String): Sort order for results. Acceptsdesc(default) orascbased on transaction timestamp.isBrc20(Boolean): Determines whether to return Fractal NFT or BRC-20 transaction records. Default istrue.orderSourceList(Integer[]): Filter transactions by marketplace source using platform codes:34: OKX54: Magic Eden55: OrdinalsWallet57: Unisat
tradeWalletAddress(String): Filter results to include only transactions involving a specific wallet address.type(String): Filter by transaction type. Accepts comma-separated values:SALE,LIST,TRANSFER,CANCEL_LIST,UPDATE_PRICE.
Default returns onlySALEevents.
These filters make it easy to build targeted queries—for example, retrieving all sales from OKX involving a particular wallet over the last week.
Response Structure: Detailed Transaction Insights
Each response returns an array of Ordinals Activities Model objects containing the following fields:
fromAddress: The sender's wallet address in the transaction.toAddress: The recipient's wallet address.inscriptionId: Unique identifier for the ordinal inscription.price: Total transaction price in FB (Fractional Bitcoin).unitPrice: Price per unit in FB, useful for bulk trades.amount: Number of inscriptions involved in the trade.timestamp: Unix timestamp indicating when the transaction occurred.isBrc20: Boolean flag indicating if the asset is a BRC-20 token (true) or Fractal NFT (false).orderSource: Numeric code representing the marketplace where the trade occurred.orderSourceName: Human-readable name of the marketplace (e.g., "OKX").type: Type of transaction (e.g., SALE, LIST).
This structured format ensures compatibility with dashboards, analytics tools, and blockchain explorers.
Practical Use Cases for Developers
1. Marketplace Analytics Dashboards
Developers can integrate this API into analytical platforms to visualize trading volume trends, top-selling collections, and cross-marketplace comparisons. By filtering via orderSourceList, you can isolate performance metrics per platform.
2. Wallet Activity Monitoring
Using the tradeWalletAddress parameter, applications can track all incoming and outgoing transactions for a given user. This is valuable for portfolio trackers and security alerts.
3. Automated Trading Bots
High-frequency trading systems benefit from real-time access to sale and listing data. With low-latency responses and precise filtering, bots can identify arbitrage opportunities across OKX and other supported platforms.
👉 Build smarter Web3 applications with reliable NFT transaction data.
Frequently Asked Questions (FAQ)
Q: What is a 'slug' in the context of Fractal Ordinals?
A: A slug is a unique string identifier assigned to each NFT collection on the Fractal platform. It's used to reference collections programmatically in API calls.
Q: Can I retrieve both NFT and BRC-20 transaction histories using this API?
A: Yes. Use the isBrc20 parameter to toggle between Fractal NFTs (false) and BRC-20 tokens (true). This allows unified access to both asset types.
Q: How do I paginate through large datasets?
A: Use the cursor parameter in combination with limit. The API returns a cursor in the response if additional pages exist, which you can pass in subsequent requests.
Q: Is there a rate limit for this API?
A: While specific rate limits depend on your access tier, it’s recommended to implement throttling logic in production applications to ensure stable performance.
Q: Can I filter transactions by multiple types at once?
A: Yes. Set the type parameter with comma-separated values like SALE,TRANSFER,CANCEL_LIST to retrieve mixed transaction types in one request.
Q: How frequently is the trade history updated?
A: Data is updated in near real-time, typically within seconds of confirmation on-chain, ensuring high accuracy for time-sensitive applications.
Getting Started with Web3 API Integration
To begin using the Fractal Ordinals trade history API:
- Register for API access through OKX Web3 Services.
- Obtain your authentication credentials (API key and secret).
- Construct your POST request with the required
slugand any desired filters. - Parse the JSON response to extract actionable insights.
Example request body:
{
"slug": "pixel-penguins",
"limit": "25",
"sort": "desc",
"type": "SALE,LIST"
}Example partial response:
[
{
"fromAddress": "bc1qabc...xyz",
"toAddress": "bc1qdef...uvw",
"inscriptionId": "abc123i",
"price": "0.05",
"unitPrice": "0.05",
"amount": "1",
"timestamp": 1717056000,
"isBrc20": false,
"orderSource": 34,
"orderSourceName": "OKX",
"type": "SALE"
}
]👉 Start integrating powerful marketplace APIs into your dApp now.
Final Thoughts
The Fractal Ordinals Trade History API provides developers with robust, flexible access to critical transaction data across leading Bitcoin-native marketplaces. With support for filtering by wallet, platform, type, and asset class—including both Fractal NFTs and BRC-20 tokens—it serves as a foundational tool for next-generation Web3 applications.
Whether you're analyzing market trends, monitoring user activity, or automating trades, this API delivers the speed, accuracy, and scalability needed in today's fast-moving blockchain ecosystem.
By leveraging structured responses and intuitive parameters, teams can reduce development time and focus on delivering exceptional user experiences powered by real-time blockchain insights.