> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.auxiliar.ai/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.auxiliar.ai/_mcp/server.

# DataForSEO

Proxies the entire [DataForSEO](https://dataforseo.com) REST API — SERP, Keywords Data, Backlinks, On-Page, DataForSEO Labs, Merchant, and more. Like ElevenLabs, it's a whole API surface, so the gateway mounts a **wildcard** and forwards the path after `/dataforseo/` verbatim:

```
GET|POST /dataforseo/<api path>   → https://api.dataforseo.com/<api path>
```

Because the path passes through unchanged, **new DataForSEO endpoints work without any gateway change**. Each endpoint is a `task_post` / `task_get` / `live` variant under `/v3`. The methods mirror what DataForSEO documents — `POST` for `task_post` and `live`, `GET` for `task_get`, `tasks_ready`, and `user_data`.

## Common paths

| Path                                                              | Purpose               |
| ----------------------------------------------------------------- | --------------------- |
| `POST /dataforseo/v3/serp/google/organic/live/advanced`           | Live Google SERP      |
| `POST /dataforseo/v3/keywords_data/google_ads/search_volume/live` | Keyword search volume |
| `POST /dataforseo/v3/backlinks/summary/live`                      | Backlinks summary     |
| `POST /dataforseo/v3/on_page/instant_pages`                       | On-Page analysis      |
| `POST /dataforseo/v3/dataforseo_labs/google/keyword_ideas/live`   | Labs keyword ideas    |
| `GET /dataforseo/v3/appendix/user_data`                           | Account data          |

## What the gateway injects and strips

DataForSEO authenticates with HTTP **Basic** auth (`Authorization: Basic <base64 of login:password>`) — reusing the `Authorization` header you use for your gateway token. So the gateway **overwrites** it with the injected credential:

* **The `Authorization` header is overwritten** with the secret DataForSEO Basic credential. You never send your DataForSEO login or password; your gateway token is consumed by the gateway and never reaches DataForSEO.
* DataForSEO has no query-param spelling of the credential, so nothing is dropped from the query string.

## Examples

```bash
curl -X POST "$GATEWAY/dataforseo/v3/serp/google/organic/live/advanced" \
  -H "Authorization: Bearer $TOKEN" \
  -H "Content-Type: application/json" \
  -d '[{"keyword": "coffee", "location_code": 2840, "language_code": "en"}]'
```

```bash
curl "$GATEWAY/dataforseo/v3/appendix/user_data" \
  -H "Authorization: Bearer $TOKEN"
```

The response is DataForSEO's JSON, returned unchanged. For request and response fields, follow [DataForSEO's documentation](https://docs.dataforseo.com) — the gateway does not alter them.