Access your Datarova project data programmatically through the Datarova API. Pull ASINs, keywords, ranks, trends, and more on whatever schedule you need, and integrate Datarova data directly into your own applications, dashboards, or pipelines.
Plan availability: API access is included on the new Professional, Team, and Agency plans. Professional includes 3,000 requests/month, Team 20,000, and Agency 60,000. Compare plans and limits.
When to use this
The API is the most flexible way to get data out of Datarova. Use it when you want to:
Build a custom dashboard or internal tool that reads Datarova data
Pipe data into a database, warehouse, or BI platform on your own schedule
Pull rank history for ASINs other than the primary ASIN, or for date ranges beyond the last 28 days (which is the limit on the Google Sheets integration)
Filter or query data programmatically rather than loading the whole dataset
Integrate Datarova into a tool you're building for clients or your team
If your needs are more straightforward (a daily-refreshed snapshot you can pull into Sheets, dashboards, or simple analyses), the Google Sheets integration is lower-friction and probably the right starting point.
Plan availability
The API is included on certain plans. Check the plans page to confirm your plan includes API access and to see how many requests per month it covers.
Generate an API key
The API uses an API key for authentication. To generate one:
Go to Settings → Connections.
Find the API Key card under Available Connections and click to generate a key.
Copy the key as soon as it's shown.
Important: The full API key is shown only once, immediately after you generate it. Datarova does not store the key in a way that lets us display it again later. If you lose it, you'll need to generate a new one and update anywhere the old key was being used.
Store the key somewhere secure, like a password manager or your application's secrets store. Don't commit it to source control.
To use the key, include it in the Authorization header on every request. The developer portal has the exact format and examples in your language of choice.
Rate limits and quotas
Two things govern how often you can call the API:
Monthly request quota. Each plan includes a fixed number of API requests per month. Check the pricing page for your plan's limit.
Per-endpoint rate limits. Each endpoint has its own rate limit (how many requests per second or minute you can make), to keep the API stable for everyone. The specific limits are documented per endpoint in the developer portal.
What counts as one request: today, every API call counts as one request against your monthly quota, regardless of how much data it returns. This may change in the future for endpoints that return very large amounts of data, but for now you can plan for one call equals one request.
If you go over either limit, the API returns a 429 Too Many Requests response. Back off and retry after a short wait.
The developer portal
Full endpoint reference, request and response examples, error codes, and code samples live in the developer portal.
The portal is the source of truth for which endpoints exist and what they return. We update it continuously as new endpoints ship and existing ones evolve, so always check there for the latest details.
Tips
Start in the developer portal's interactive reference to test calls before writing any code. You can copy working examples in your language directly from there.
Build your integration to handle 429 responses gracefully with exponential backoff. Even if you're nowhere near your monthly quota, transient bursts can hit per-endpoint limits.
Cache data on your side rather than re-fetching the same data every time you need it. This protects your quota and reduces load on the API.
Treat your API key like a password. Anyone with the key can read your Datarova data, so rotate it if you ever suspect it's been exposed.