SEO API | SpideyData

SEO API endpoints

24

Find the task you need. Each endpoint includes its parameters, request example, and response reference.

Retrieve live search engine results

Run a bounded search request and inspect its normalized search results.

Research keyword ideas, volume and metrics

Choose suggestions, related keywords, overview metrics, search volume or advertising keyword ideas.

Find competitors in search results

Identify SERP competitors for the keywords and targeting supported by the request.

Check SEO API capability availability

Read the capability directory before selecting an execution task.

Find supported search locations

Look up supported location values to use in search and keyword requests.

Inspect saved SEO API requests

Use a request ID to read the saved record authorized for your Team.

Analyze backlinks and referring domains

Read backlink summaries, individual links, referring domains, linked pages and historical data.

Research brand mentions and compare visibility

Search mentions, inspect metrics and top pages, or compare brand metrics.

Request model answers and discover available models

Read model IDs, then request answers through the ChatGPT, Claude or Gemini endpoints.

Quick start

Read /v1/seoapi/capabilities for availability and prices, /v1/seoapi/locations for markets, and /v1/seoapi/llm/{platform}/models for free model catalogs.

API base https://kieapi.com

curl -X POST "https://kieapi.com/v1/seoapi/serp/search" \
  -H "Authorization: Bearer $SPIDER_API_KEY" \
  -H 'Idempotency-Key: seoapi-example-01' \
  -H "Content-Type: application/json" \
  -d '{
  "keyword": "example keyword",
  "country": "us",
  "language": "en",
  "limit": 10
}'

Authentication

Use a bearer token.

Team administrators manage API keys in Team Settings. Each key keeps its Team and billing scope when its creator leaves or switches Teams. Keys cannot manage members, billing or other keys. Public /v1 requests use Authorization: Bearer $SPIDER_API_KEY only; the Key's fixed Team is the payer. An optional X-Spider-Team-Id must match that Team or the request is denied. Creating, listing, rotating or revoking Keys through the product console (and other non-identity console business routes) requires X-Spider-Team-Id when the Team model is enabled; omitting it returns HTTP 409 team_context_required.

Data, sources and delivery

Twenty capabilities

Live SERP search; keyword suggestions, ideas, related keywords and overview; SERP competitors; Google Ads search volume and keyword ideas. Also includes five backlink tasks, four AI brand mention tasks and ChatGPT/Claude/Gemini answers. Free model catalogs provide current model IDs.

Explicit sources

source identifies provider, dataset, method, market and observation time. Live search and keyword database results have different freshness. Missing values remain null. Ads competition is distinct from keyword difficulty. SERP result_count_estimate is separate from the returned row count.

Exactly-once delivery

An operator or admin role and Idempotency-Key are required. Reuse the same key after a lost response. Complete delivery costs 20 Credits per request across all twenty capabilities; partial or failed delivery releases Credits. Bounded batches count once, and free GETs and same-key replays add no charge. Unknown provider delivery is not resubmitted. GET /v1/seoapi/requests/{request_id} reads the saved Team request; errors include X-SEOAPI-Request-ID.

Bounded inputs

Metrics and competitors accept up to 100 keywords. Ideas accept up to 20 seeds. SERP depth is 1–100; list limits are 1–1000. Ads ideas reports local truncation. Missing requested keywords produce partial coverage without a charge. Prices are configured per capability; unconfigured prices are unavailable.