DataForSEO
Proxies the entire DataForSEO 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:
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
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
Authorizationheader 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
Live SERP (POST)
Account data (GET)
The response is DataForSEO’s JSON, returned unchanged. For request and response fields, follow DataForSEO’s documentation — the gateway does not alter them.