🧮 How Data API Credits Are Counted (and When a Call Costs 0)
Credits measure the data you get back, per product, not per request.
Last reviewed
Every Data API plan includes a monthly credit allowance: 1,000 on Starter, 10,000 on Professional, 50,000 on Enterprise. Each call costs credits for the data it returns.
What each call costs
| Operation | Cost | |---|---| | Product details | 1 credit per product found | | Keyword search | 1 credit per product returned | | Current offers, all retailers | 3 credits per product | | Current offers, one retailer | 2 credits per product | | Price history | Offer cost per product + 1 credit per day of the window, the per-day part charged once per request | | Schedule monitoring | 1 credit per product; refreshes are free | | Deals | 1 credit per 10 deals | | TLDR review | 1 credit when a review exists |
When a call costs 0
- Identifiers that match nothing.
- Products with no offers on the offers and history endpoints (the history day charge too).
- A review request for a product with no review.
GET /v1/usage, and every error response.
Credits and the rate limit are separate
The rate limit is 1,000 requests per rolling hour per account. A request that costs 0 credits still counts as a request, so send up to 100 identifiers per call.
Worked example
Price history for 1 product over 90 days costs 1 × 3 + 90 = 93 credits. The same window for 10 products in one request costs 10 × 3 + 90 = 120 credits, not 930.
Plans and prices: shopsavvy.com/pricing.