Real-time Data
Understanding real-time data and its use cases
Since the inception of SneakersAPI, our primary goal has been to store data in our database to enhance its usability for you. This approach allows us to aggregate, clean, and present data through a faster and more reliable API, unaffected by rate limits or bans from our data sources.
However, there are scenarios where you might need the most up-to-date information or want data in a specific country and currency other than the US and USD, the default settings for SneakersAPI.
To address these needs, we introduced the Real-time Data feature in API v3, also known as Proxied Requests. This functionality enables direct requests to StockX and GOAT APIs, providing real-time data straight from the source.
While real-time requests are inherently slower than accessing stored data, we’ve optimized the process to deliver industry-leading performance. Currently, our real-time service boasts an average response time of 1.3 seconds and a 99% success rate.
When to Use Real-time Data
Real-time data is available exclusively in the pro-tier and is limited to 120 requests per minute to prevent abuse. We recommend using this feature in the following cases:
- When you require the most up-to-date product information.
- When you need market data for countries and currencies other than the US and USD.
- When you can accommodate slightly slower response times.
- When you can deal with the occasional request failure.
Stored data is refreshed every 12 hours. If you need data that is more current, opt for real-time data.
Recommendations
SneakersAPI is already scraping data regularly and storing it in our database, allowing you to access it quickly with a much higher rate limit.
Due to the rate limit, we don’t recommend using the real-time endpoints for user-facing applications. Instead, we recommend making occasional requests to the real-time endpoints to store or cache the data in your database.