nabu.readme.io
Open in
urlscan Pro
2606:4700::6812:d238
Public Scan
URL:
https://nabu.readme.io/reference/introduction
Submission: On January 24 via api from PL — Scanned from DE
Submission: On January 24 via api from PL — Scanned from DE
Form analysis 0 forms found in the DOM
Text Content
Jump to Content API Reference v0.1 -------------------------------------------------------------------------------- Log In API Reference Log In v0.1API Reference Search CTRL-K Getting StartedIntroductionRequest API KeyNabuPrices by TokenPrices by Token (historical)Prices by CollectionPrices by WalletCollection AnalyticsCollection Analytics (historical)Listed Tokens by CollectionModel SchemaTokenCollection StatsValue Driver All Reference START TYPING TO SEARCH… JUMP TOCTRL-/ GETTING STARTED * Introduction * Request API Key NABU * Prices by Tokenget * Prices by Token (historical)get * Prices by Collectionget * Prices by Walletget * Collection Analyticsget * Collection Analytics (historical)get * Listed Tokens by Collectionget MODEL SCHEMA * Token * Collection Stats * Value Driver Powered by JUMP TOCTRL-/ GETTING STARTED * Introduction * Request API Key NABU * Prices by Tokenget * Prices by Token (historical)get * Prices by Collectionget * Prices by Walletget * Collection Analyticsget * Collection Analytics (historical)get * Listed Tokens by Collectionget MODEL SCHEMA * Token * Collection Stats * Value Driver Powered by INTRODUCTION The Nabu REST API has methods for querying our database of price estimates. If you don't yet have an API key, visit the Request API Key page to apply for one. If you already have the key, remember to always pass its value in the x-api-key header when making requests. API keys are usually rate limited, and will allow up to 10 requests per second with a burst (concurrency) of 50 requests. Not every collection has price estimates. We currently support PFP collections that fulfill at least the following criteria: * a sufficient number of tokens minted * a sufficient number of traits in the tokens metadata * sufficient sales history for at least some tokens What constitutes sufficient may vary depending on the abundance of data in other criteria. If when querying the latest price for a token you receive a contract_status of pending, that means that we have queued that collection to be priced for the first time now (your query has effectively "added" the collection to our database), and after a couple of minutes a new query for that token might return an estimated price. Updated about 2 months ago -------------------------------------------------------------------------------- What’s Next * Request API Keyarrow-right Did this page help you? Yes No Updated about 2 months ago -------------------------------------------------------------------------------- What’s Next * Request API Keyarrow-right Did this page help you? Yes No 1. Getting Started 2. Introduction 3. Request API Key 1. Nabu 2. Prices by Tokenget 3. Prices by Token (historical)get 4. Prices by Collectionget 5. Prices by Walletget 6. Collection Analyticsget 7. Collection Analytics (historical)get 8. Listed Tokens by Collectionget 1. Model Schema 2. Token 3. Collection Stats 4. Value Driver 1. Getting Started 2. Introduction 3. Request API Key 1. Nabu 2. Prices by Tokenget 3. Prices by Token (historical)get 4. Prices by Collectionget 5. Prices by Walletget 6. Collection Analyticsget 7. Collection Analytics (historical)get 8. Listed Tokens by Collectionget 1. Model Schema 2. Token 3. Collection Stats 4. Value Driver