# DataForSEO Labs Historical SERPs API

> Past Google search results for a keyword within a date range.

Source: https://www.sandbase.ai/apis/dataforseo/v3/dataforseo_labs/google/historical_serps/live
API reference: https://www.sandbase.ai/apis/dataforseo/v3/dataforseo_labs/google/historical_serps/live/docs

## Facts

- Provider: DataForSEO
- Type: Data API
- Endpoint: `POST https://api.sandbase.ai/v1/api/dataforseo/v3/dataforseo_labs/google/historical_serps/live`
- Price: From $0.0002 per call
- Capabilities: labs, serp, history
- Billing: pay per use from one SandBase balance; no provider account or subscription needed

## Call it

`POST https://api.sandbase.ai/v1/api/dataforseo/v3/dataforseo_labs/google/historical_serps/live` with `Authorization: Bearer $SANDBASE_API_KEY` and the parameters as a JSON body.

## FAQ

### How do I use the DataForSEO Labs Historical SERPs API?

Send a POST request to https://api.sandbase.ai/v1/api/dataforseo/v3/dataforseo_labs/google/historical_serps/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 Labs Historical SERPs API cost?

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

### What parameters does the DataForSEO Labs Historical SERPs API accept?

DataForSEO Labs Historical SERPs takes no input parameters; send an empty JSON body.

### What does the DataForSEO Labs Historical SERPs API return?

A JSON response returned in the same HTTP request (synchronous).

### Do I need a DataForSEO developer account or API key?

No. DataForSEO Labs Historical SERPs 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.

## README

### DataForSEO Labs Historical SERPs API

Past Google search results for a keyword within a date range.

Request fields follow the official DataForSEO `/v3/dataforseo_labs/google/historical_serps/live` task schema (one task per call). The response is DataForSEO's original JSON; results are in `tasks[].result`.

#### Request

```bash
curl -X POST "https://api.sandbase.ai/v1/api/dataforseo/v3/dataforseo_labs/google/historical_serps/live" \
  -H "Authorization: Bearer $SANDBASE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"keyword": "coffee", "location_code": 2840, "language_code": "en", "date_from": "2026-06-01"}'
```

#### Parameters

The JSON body is forwarded to the upstream endpoint. Main fields:

| Name | Description |
|---|---|
| `keyword` | Keyword. |
| `location_code` | Location code, e.g. 2840 for the United States. |
| `language_code` | Language code, e.g. "en". |
| `date_from` | Optional start date, "yyyy-mm-dd". |
| `date_to` | Optional end date. |

#### Reference

- Official docs: https://docs.dataforseo.com/v3/dataforseo_labs/google/historical_serps/live/

#### Pricing

Billed at the actual cost of each call, about $0.00024 for the request above. The cost grows with the number of rows, targets or tokens a call returns. Failed calls are not charged. Searches with no results are billed at their actual cost.