DataForSEO — Dataforseo Labs / Amazon / Bulk Search Volume / Live

Retrieve labs Amazon Bulk Search Volume Live with the DataForSEO API. The sample response includes keywords. Use it to prioritize keywords for content research. Use the results to organize a research workflow and cross-check the relevant source records.

Selected price
$0.012 base + $0.00012 / result Published pricing
Sellers / implementations
1 / 1
Requests · 30d
—Loading...
Success rate · 30d
—Loading...

Run sends a real API request. Charges follow the published API contract.

Request parameters
body* array
body[0]* object | null
keywords* array
target keywords required field UTF-8 encoding maximum number of keywords you can specify in this array: 1000; the keywords will be converted to lowercase format learn more about rules and limitations of keyword and keywords fields in DataForSEO APIs in this Help Center article
Optional parameters (5)
language code required field if don't specify language_name you can receive the list of available languages with their language_code by making a separate request to https://api.dataforseo.com/v3/dataforseo_labs/locations_and_languages Note: this endpoint currently supports these locations and languages only; example: en
full name of the language required field if don't specify language_code you can receive the list of available languages with their language_name by making a separate request to https://api.dataforseo.com/v3/dataforseo_labs/locations_and_languages Note: this endpoint currently supports these locations and languages only; example: English
location code required field if don't specify location_name you can receive the list of available locations with their location_code by making a separate request to https://api.dataforseo.com/v3/dataforseo_labs/locations_and_languages; Note: this endpoint currently supports these locations and languages only; example: 2840
full name of the location required field if don't specify location_code you can receive the list of available locations with their location_name by making a separate request to https://api.dataforseo.com/v3/dataforseo_labs/locations_and_languages; Note: this endpoint currently supports the following locations and languages only: Australia - 2036, en Austria - 2040, de Canada - 2124, en Egypt - 2818, ar France - 2250, fr Germany - 2276, de India - 2356, en Italy - 2380, it Mexico - 2484, es Netherlands - 2528, nl Saudi Arabia - 2682, ar Singapore - 2702, en Spain - 2724, es United Arab Emirates - 2784, ar United Kingdom - 2826, en United States - 2840, en example: United States
user-defined task identifier optional field the character limit is 255 you can use this parameter to identify the task and match it with the result you will find the specified tag value in the data object of the response
‌ This endpoint will provide you with search volume values for a maximum of 1,000 keywords in one API request. Here search volume represents the approximate number of monthly searches for a keyword on Amazon. The returned results are specific to the keywords, location, and language parameters specified in a POST request.

Sample response

{
  "cost": 0.0103,
  "status_code": 20000,
  "status_message": "Ok.",
  "tasks": [
    {
      "cost": 0.0103,
      "data": {
        "api": "dataforseo_labs",
        "function": "bulk_search_volume",
        "keywords": [
          "phone",
          "iphone",
          "samsung"
        ],
        "language_name": "English",
        "location_code": 2840,
        "se_type": "amazon"
      },
      "id": "03021533-0696-0397-0000-ac4576a471ea",
      "path": [
        "v3",
        "dataforseo_labs",
        "amazon",
        "bulk_search_volume",
        "live"
      ],
      "result": [
        {
          "items": [
            {
              "keyword": "phone",
              "se_type": "amazon",
              "search_volume": 39000
            },
            {
              "keyword": "iphone",
              "se_type": "amazon",
              "search_volume": 69500
            },
            {
              "keyword": "samsung",
              "se_type": "amazon",
              "search_volume": 31800
            }
          ],
          "items_count": 3,
          "language_code": "en",
          "location_code": 2840,
          "se_type": "amazon",
          "total_count": 3
        }
      ],
      "result_count": 1,
      "status_code": 20000,
      "status_message": "Ok.",
      "time": "0.0418 sec."
    }
  ],
  "tasks_count": 1,
  "tasks_error": 0,
  "time": "0.0919 sec.",
  "version": "0.1.20220216"
}

Response result

Response structure

Inferred from examples
  • costnumber
  • status_codeinteger
  • status_messagestring
  • tasksobject[]
    • costnumber
    • dataobject
      • apistring
      • functionstring
      • keywordsstring[]
      • language_namestring
      • location_codeinteger
      • se_typestring
    • idstring
    • pathstring[]
    • resultobject[]
      • itemsobject[]
        • keywordstring
        • se_typestring
        • search_volumeinteger
      • items_countinteger
      • language_codestring
      • location_codeinteger
      • se_typestring
      • total_countinteger
    • result_countinteger
    • status_codeinteger
    • status_messagestring
    • timestring
  • tasks_countinteger
  • tasks_errorinteger
  • timestring
  • versionstring

Common questions

Do I need a separate key for every provider?

Use your OpenAny API key for standard API access. Read it from OPENANY_API_KEY in your environment and keep it out of prompts, source code and logs.

Are these providers interchangeable?

No. Each offering has its own inputs, pricing and response contract. Selecting a catalog offering does not establish automatic routing or fallback. Confirm the service contract before calling.

How is this API billed?

API-key calls use your shared balance at the selected implementation's published rate. Check the billing unit and request-specific pricing rules before making a paid call. Recorded usage determines the final charge under that contract.

Where do the price and contract come from?

The selected implementation publishes its provider, request contract, revision and billing rules through OpenAny's public API catalog. A revision number identifies a contract version, not a price update date. A price update timestamp is not supplied; do not treat a page date as one.

How do OpenAny Balance and x402 differ?

OpenAny Balance uses an API key and one shared balance. Card, USDC and x402 top-ups, card auto top-up and USDC subscriptions fund that balance; available routes appear on the Credits page. Direct x402 is a separate pay-per-request flow, available only on listings that show it and requiring an authorized payment client.

Does Playground send a paid request?

Yes. After you sign in, Run sends a real API request using an active OpenAny API key. Charges follow the published API contract and use your shared balance. Selecting an implementation, editing inputs and viewing sample responses do not send requests.

Use DataForSEO — Dataforseo Labs / Amazon / Bulk Search Volume / Live with your agent

Inspect endpoint contracts and confirm availability and pricing before a paid call.