Start building

DataForSEO Google Historical Search Volume

https://api.sandbase.ai/v1/api/dataforseo/v3/dataforseo_labs/google/historical_search_volume/live

Get historical Google search volume for keywords from DataForSEO Labs: monthly searches, CPC, competition and keyword properties by location and language.

Try this APIGet API key
Price
$0.02USD / call
Method
POST
Response
JSON
Parameters
0 required · 0 optional
Production route

Try the model

Playground

Open playground
Input
No input schema available
OutputExample
Responseoutputs · 744 B · 34 lines
[
  {
    "cost": 0,
    "status_code": 20000,
    "status_message": "Ok.",
    "tasks": [
      {
        "cost": 0,
        "data": {
          "api": "dataforseo_labs",
          "function": "historical_search_volume",
          "se_type": "google"
        },
        "id": "08200930-2190-0401-0000-6b5ddc3fc3ab",
        "path": [
          "v3",
          "dataforseo_labs",
          "google",
          "historical_search_volume",
          "live"
        ],
        "result": null,
        "result_count": 0,
        "status_code": 40503,
        "status_message": "POST Data Is Invalid.",
        "time": "0 sec."
      }
    ],
    "tasks_count": 1,
    "tasks_error": 1,
    "time": "0.0385 sec.",
    "version": "0.1.20260806"
  }
]

Examples

Select an example to load its inputs and result into the playground.

Model card

Specifications

Pricing

Base price
$0.02 / run

Request & response

Method
POST
Request body
application/json
Response
application/json
Execution
sync

Parameters

Parameters
None

Access

Provider
DataForSEO
API
Platform API
Base URL
https://api.sandbase.ai
Endpoint
/v1/api/dataforseo/v3/dataforseo_labs/google/historical_search_volume/live
Authentication
Bearer API key

API README

Google Historical Search Volume API

Send keywords with a location and language and get their search volume history and keyword metrics.

Use cases

  • Analyze seasonality and long-term demand.
  • Compare keyword trends year over year.
  • Prioritize SEO keywords.

Request

curl -X POST "https://api.sandbase.ai/v1/api/dataforseo/v3/dataforseo_labs/google/historical_search_volume/live" \
  -H "Authorization: Bearer $SANDBASE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"keywords": ["running shoes"], "location_code": 2840, "language_code": "en"}'

Parameters

The body is passed through to DataForSEO. Common fields:

NameTypeDescription
keywordsarrayKeywords to look up.
location_codeintegerDataForSEO location code, e.g. 2840 for the United States.
language_codestringLanguage code, e.g. "en".

Example response

Real response for the request above, trimmed to the main fields. User names and long IDs are masked.

{
  "status_code": 20000,
  "tasks": [
    {
      "result": [
        {
          "items": [
            {
              "keyword": "openai api",
              "location_code": 2840,
              "keyword_info": {
                "search_volume": 49500,
                "cpc": 11.63,
                "competition": 0.07,
                "competition_level": "LOW",
                "last_updated_time": "2026-09-16 14:09:04 +00:00",
                "monthly_searches": [
                  {
                    "month": 8,
                    "search_volume": 49500,
                    "year": 2026
                  },
                  {
                    "month": 7,
                    "search_volume": 49500,
                    "year": 2026
                  }
                ]
              }
            }
          ]
        }
      ]
    }
  ]
}

Pricing

Flat price per call. Failed calls are not charged.

Related APIs

Start building

Send your first request

Platform API endpoint with unified authentication and usage tracking.

Production API
Platform API endpoint
https://api.sandbase.ai/v1/api/dataforseo/v3/dataforseo_labs/google/historical_search_volume/live
Authorization header
Authorization: Bearer $SANDBASE_API_KEY
# The quoted heredoc keeps Unicode and shell metacharacters unchanged.
result=$(curl --fail-with-body --silent \
  -X POST "https://api.sandbase.ai/v1/api/dataforseo/v3/dataforseo_labs/google/historical_search_volume/live" \
  -H "Authorization: Bearer $SANDBASE_API_KEY" \
  -H "Content-Type: application/json" \
  --data-binary @- <<'SANDBASE_JSON'
{}
SANDBASE_JSON
)
printf '%s\n' "$result"

Explore more

Related APIs

All APIs
APIPriceResponseReleased
DataForSEO Google Historical Search VolumeThis API
DataForSEO		$0.02 per callJSONJan 1, 2024
DataForSEO ChatGPT Search Answer
DataForSEO		$0.004 per callJSONJan 1, 2024
DataForSEO Gemini Search Answer
DataForSEO		$0.004 per callJSONJan 1, 2024
DataForSEO Backlinks Anchors
DataForSEO		$0.004 per callJSONJan 1, 2024
DataForSEO Backlinks List
DataForSEO		$0.004 per callJSONJan 1, 2024
DataForSEO Backlinks Bulk Ranks
DataForSEO		$0.002 per callJSONJan 1, 2024

Questions

FAQ

How do I use the DataForSEO Google Historical Search Volume API?

Send a POST request to https://api.sandbase.ai/v1/api/dataforseo/v3/dataforseo_labs/google/historical_search_volume/live with your SandBase API key in the Authorization header (Bearer) and the parameters as a JSON body. You can also try it in the Playground on this page without writing code.

How much does the DataForSEO Google Historical Search Volume API cost?

$0.02 per call, billed from your SandBase balance. You are only charged for calls you make; there is no subscription.

What parameters does the DataForSEO Google Historical Search Volume API accept?

DataForSEO Google Historical Search Volume takes no input parameters; send an empty JSON body.

What does the DataForSEO Google Historical Search Volume API return?

A JSON response returned in the same HTTP request (synchronous). The README on this page includes a sample response.

Do I need a DataForSEO developer account or API key?

No. DataForSEO Google Historical Search Volume runs through SandBase, so one SandBase API key covers this endpoint and every other API and model in the catalog. You do not need to apply for DataForSEO API access separately.