Core APIs
...
Core Requests
Search + Product
5 min
search + product request live requests only not supported for batches make a type=search request and choose how many of the top search results should have product requests run control the number of search results returned number of results= and the number of corresponding product requests include products count= to run to build a search and/or product request, refer to https //docs trajectdata com/rainforestapi/product data api/parameters/product and https //docs trajectdata com/rainforestapi/product data api/parameters/search pages for example, to request search results for the search term "memory cards", and run product requests for the top ten search results,on amazon com , the request would be http https //api rainforestapi com/request?api key=demo\&type=search\&amazon domain=amazon com\&search term=memory+cards\&include products count=10 note each product request counts as +1 credit the base search costs 1 credit, and for every result included in include products count, an additional 1 credit is charged if you set include products count = 10 , the total cost will be 1 (search) + 10 (products) = 11 credits use case and benefits benefit 1 improved api efficiency – the ability to make a single type=search api call and automatically fan out into type=product requests reduces the need for multiple manual api calls, streamlining data retrieval benefit 2 significantly faster response times – various optimization strategies, such as limiting the number of search results, excluding sponsored results, selectively retrieving only necessary fields, will improve response times benefit 3 flexible data selection – users can control the number of search results returned (number of results=) and the number of corresponding product requests (include products count=), optimizing the balance between speed and data completeness benefit 4 parallel processing for maximum speed – the system executes product requests in parallel, ensuring that fetching product details does not create unnecessary sequential delays benefit 5 customizable field selection for performance gains – using the fields= parameter, users can limit api responses to only the essential data, leading to additional speed improvements and reduced payload size example a search request that returns 10 results, runs product requests for those 10 results (excluding any sponsored listings), and only retrieves specific fields in the json response https //api rainforestapi com/request?api key=\<api key>\&type=search\&amazon domain=amazon com\&search term=paranormal+detective\&number of results=10\&include products count=10\&exclude sponsored=true\&fields=search results price,search results product bestsellers rank,search results product specifications,search results product publication date next steps https //docs trajectdata com/rainforestapi/product data api/results/search product