SERP

Overview & Purpose

GET /serp answers a different question than the other endpoints: not “what’s on this page?” but “what do the search results say?” It returns parsed organic results, not raw search-results HTML. Use it when you need search results themselves — rank tracking, competitive research, “what’s currently ranking for X” — rather than the content of a page you already have the URL for. If you already have a URL, use Scrape instead. Prerequisites: a valid API key. No special scope required.

Best practices

Not every field is always returned. Knowledge graph, People Also Ask, sitelinks, and an estimated result total are all best-effort — treat their absence as normal, not an error.
Localize with country and language rather than embedding location terms in query — it’s more reliable and doesn’t cost extra query length.
Set a tag per keyword or campaign so you can filter and trace searches in Request history.

Practical Implementation Example

Scenario: get the top ranked pages for a keyword, as seen from a specific country and language.

curl -G "https://apix.pline.ai/v1/serp" \
  -H "X-API-Key: $API_KEY" \
  --data-urlencode "query=best running shoes" \
  --data-urlencode "country=US" \
  --data-urlencode "language=en" \
  --data-urlencode "tag=rank.running-shoes"

import os
import httpx

response = httpx.get(
    "https://apix.pline.ai/v1/serp",
    headers={"X-API-Key": os.environ["API_KEY"]},
    params={"query": "best running shoes", "country": "US", "language": "en", "tag": ["rank.running-shoes"]},
    timeout=60.0,
)
response.raise_for_status()
results = response.json()["organic"]
for result in results:
    print(result["position"], result["title"], result["link"])

const params = new URLSearchParams({
  query: "best running shoes",
  country: "US",
  language: "en",
  tag: "rank.running-shoes",
});

const response = await fetch(`https://apix.pline.ai/v1/serp?${params}`, {
  headers: { "X-API-Key": process.env.API_KEY },
});

const { organic } = await response.json();
organic.forEach((r) => console.log(r.position, r.title, r.link));

Error codes

Code	When you receive it
`400`	Malformed query parameters.
`422`	An invalid parameter value — e.g. an empty `query`, or an invalid `country`/`language` code.
`429`	The search rate limit was reached. Retry after a short delay.
`502`	The search returned an invalid or blocked response.
`503`	Search is unavailable.
`504`	The search request timed out.

Get started

Endpoints

Teams

Billing

Monitoring

Overview & Purpose

Best practices

Practical Implementation Example

Error codes

Reference Links

​Overview & Purpose

​Best practices

​Practical Implementation Example

​Error codes

​Reference Links

Overview & Purpose

Best practices

Practical Implementation Example

Error codes

Reference Links