Amazon SP-API Now Supports Multi-ASIN Queries in Search Query Performance Reports
In early 2024 Amazon expanded the GET_BRAND_ANALYTICS_SEARCH_QUERY_PERFORMANCE_REPORT SP‑API endpoint to accept a space‑separated list of ASINs (up to 200 characters, roughly 18 ten‑character ASINs). This lets brand‑registered sellers pull search‑term data for multiple products in a single call, keeping the same rate limits but dramatically reducing call volume.
Overview
Amazon has enhanced the Search Query Performance Report endpoint in the Selling Partner API (SP‑API) to accept a list of ASINs in a single request. The change, rolled out globally in early 2024, lets brand‑registered sellers pull search‑term data for roughly 18 products at once instead of one‑by‑one. Reducing the number of calls needed speeds up portfolio‑level analytics and frees up API quota for other operations.
Key Points
- Batch size limit — Each request can contain up to 200 characters, which translates to about 18 standard 10‑character ASINs separated by spaces.
- Endpoint unchanged — The same
GET_BRAND_ANALYTICS_SEARCH_QUERY_PERFORMANCE_REPORTURL is used; only theasinparameter now supports multiple values. - Rate limits stay the same — Amazon has not altered the per‑minute or per‑day throttling rules, so efficiency gains come solely from packing more data into each call.
- Full backward compatibility — Single‑ASIN queries continue to work exactly as before, ensuring existing integrations do not break.
- Global coverage — The multi‑ASIN capability is active across all Amazon marketplaces, from the US and EU sites to Japan and newer regions.
- Immediate quota impact — A seller who previously needed 100 calls to evaluate 100 SKUs can now cover up to 1,800 SKUs with the same quota, assuming optimal batching.
How Multi‑ASIN Queries Work
- Compose a space‑separated ASIN string — List the desired ASINs in the
asinquery parameter, e.g.,asin=B01N5IB20Q B07PGL2ZJ5 B08L5V5Z9K. The API treats the space as a delimiter and returns data for all three products in one payload. - Observe the 200‑character ceiling — Count characters including spaces; a string of 18 ASINs (
B0XXXXXXXXrepeated) reaches roughly 200 characters. If the limit is exceeded, the request returns an error, so sellers must trim or split the list. - Send the request as usual — Use the same authentication headers, marketplace ID, and date range parameters that were required for single‑ASIN calls. The response format mirrors the original, delivering a row for each ASIN‑keyword combination.
Analysis & Recommendations
Why This Matters
A seller who previously needed 100 separate API calls for 100 SKUs can now retrieve data for up to 1,800 SKUs with the same quota, cutting calls from 100 to about 7 batches. This speeds portfolio‑level analytics, frees quota for other endpoints, and enables near‑real‑time dashboards during high‑traffic events like Prime Day.
Key Takeaways
- Batch size limit is 200 characters, which equals roughly 18 standard 10‑character ASINs per request.
- The endpoint URL remains GET_BRAND_ANALYTICS_SEARCH_QUERY_PERFORMANCE_REPORT; only the asin parameter now supports multiple values.
- Rate limits (per‑minute and per‑day) are unchanged, so efficiency gains come from packing more ASINs per call.
- A brand with 120 SKUs can reduce calls from 120 to 7 batches, saving up to 93% of its API quota usage.
Recommended Actions
- →Update your data‑pull scripts (e.g., Python src/api.py or Node src/api.js) to join ASIN arrays with spaces and pass them to the asin query parameter.
- →Create a utility that splits ASIN lists into 200‑character chunks and schedule batch requests in Seller Central > Reports > API Integration.
- →Monitor quota usage in the SP‑API console and reallocate saved calls to other endpoints such as Inventory or Pricing.
Comments
Join the discussion
Log in or create an account to share your thoughts on this update.
No comments yet. Be the first to share your thoughts!