Over the last few months, our team has been hard at work shipping new API endpoints to help developers access the NFT data they need to build NFT experiences on dApps and more! This month, we will be spotlighting one major class of endpoints, Time Series, which provides a convenient way for you to retrieve NFT data over time.
Spotlighting our Time Series endpoints
This is a category of Gomu API Endpoints we have had available for a few months now, and we will be shedding more light on how these endpoints can be used and the information you can expect to get from each of the endpoints.
In general, the data returned by these endpoints are used in charts to display the data over a period of time. Some commonalities between them are that these endpoints accept a start time and an optional end time for you to define a time period to be querying data for. They also allow you to specify how you want the data to be further segmented down either by day, week, month or year.
Now, let’s drill into the specifics of each endpoint below!
1. Transaction Count
/rest/timeseries/transaction-count returns the on-chain transaction count of a specified collection. This is specifically the number of transactions that happened, and it does not return the sales volume of the transaction (there is a specific endpoint for that, listed below).
View our sample call: Monthly Azuki transaction counts from March to October
For more information, see the Time series data for transaction count documentation.
2. Floor Price
/rest/timeseries/floor-price returns the average floor price of a specified collection, with the values being available in both ETH and USD, to save you time from having to do the conversions. The data from this endpoint helps you to see how the floor price of a collection has been trending over different periods of time.
View our sample call: Weekly MAYC Floor Price from August 2 until now
For more information, see the Time series data for floor price documentation.
3. Contract Owners
/rest/timeseries/owners-count returns the average number of owners of a specified collection.
View our sample call: Daily average # of owners of Isekai Meta from October 31, 2022 until now
For more information, see the Time series data for contract owners documentation.
4. Contract Volume
/rest/timeseries/volume returns the total sales volume of a collection broken down by your specified granularity value. This can be used along with the transaction count endpoint to get a clearer picture of how active a collection is, by seeing how many trades happened over a period of time alongside the total value of those trades.
View our sample call: Monthly trade volume of CryptoPunks since June 1, 2022
For more information, see the Time series data for contract volume documentation.
5. Wallet Holdings
/rest/timeseries/wallet takes in a contract address and a wallet address, and returns the number of NFTs the wallet has held from the specified collection over a period of time. This is especially useful for keeping track of how the holdings of different whale wallets across different collections shift overtime.
View our sample call: Monthly # of Apes held by Dingaling.eth since June
For more information, see the Time series data for a specific wallet's holdings documentation.
6. Top Owners
/rest/timeseries/top-owners returns the wallet addresses of the top holders of a specified contract. The endpoint allows you to specify how many top holders you want to be returned in the response.
View our sample call: Monthly Top 5 Moonbirds holders since May
For more information, see the Time series data for top owners of a contract documentation.
New filter parameters for our /rest/nfts/by-X endpoints
For our /rest/nfts/by-contract, /rest/nfts/by-token & /rest/nfts/by-wallet endpoints, we have three new parameters (in bold) which you can use to filter out non-required data in the response, with the aim of making each of these endpoints more lightweight.
- The lastTransfer object is now omitted from the response by default. This can still be included by using the new includeLastTransfer parameter and setting its value to true.
- We have added parameters to omit the orderbook and owners data from our response. These will still be part of the response by default but can be excluded by using the skipOrderbook and skipOwners parameters respectively and setting their values to true.
View our sample call: BAYC tokens including their last transfer data
For more information, see the Gomu NFT APIs documentation.
PolyientX is a Web3 platform that helps creators and brands reward NFT collectors. The PolyientX platform allows creators and brands to easily create rewards like merch, coupon codes, event passes and more. NFT collectors can redeem rewards by verifying NFT ownership on a custom-branded rewards page.
The team is excited about the future of NFTs and we are excited to work with PolyientX to achieve their vision! Gomu is helping PolyientX by providing their platform with metadata of NFTs across different blockchains. The metadata connects to a custom-built dashboard by PolyientX which provides insights about NFT collector activity.
To all the builders out there, reach out to us here if you are building and launching with the Gomu API. We will love to feature your product in our upcoming monthly updates. Till then, happy building everyone!