Synchronous requests
Real-Time SERP API
Real-time = same response.
Here, real-time means synchronous: you POST a query and the parsed results come back in the same HTTP response. No latency numbers are published. When volume matters more than immediacy, Google queries can move to tasks.
Baidu and Ecosia endpoints opening soon.
curl -s -X POST https://kieapi.com/v1/serp/google/news \
-H "Authorization: Bearer $KEY" -H "Content-Type: application/json" -d '{"q":"central bank decision","hl":"en"}' \
| jq '.news_count'Sync request lifecycle
- Your POST arrives with the query and engine.
- The results page is fetched and parsed server-side.
- Success: 200 with normalized JSON, charged once at 2 Credits (display rate).
- Failure: an error status (for example 502 FetchFailed), and the failed search is not charged.
When to queue instead
A user is waiting on the answer
Use: Sync endpoint
Hundreds of Google keywords, results needed later
Use: POST /v1/serp/google/{vertical}/tasks, then poll
Bing, Yahoo, DuckDuckGo, Baidu or Ecosia
Use: Sync only; these engines have no task queue
No latency SLA
No response-time target, QPS figure or uptime SLA is published. Design timeouts and retries on your side.
Launch status for this page
Check engine availability before choosing an endpoint. Google also supports News, Images and asynchronous tasks.
- GoogleGoogle is callable today with a Bearer API key.
- BingBing is callable today with a Bearer API key.
- YahooYahoo is callable today with a Bearer API key.
- DuckDuckGoDuckDuckGo is callable today with a Bearer API key.
- BaiduBaidu endpoints opening soon: until they open, requests return 503 service_unavailable and are not charged.
- EcosiaEcosia endpoints opening soon: until they open, requests return 503 service_unavailable and are not charged.
SERP searches are charged per successful search at a display rate of 2 Credits per search; failed searches are not charged. Polling task status is free. The current rate is on Pricing.
What this is not
- No latency or QPS figures.
- No speed claims.
- No queue for non-Google engines.
- No webhook.
Frequently asked questions
Is the response synchronous?
Yes. Sync endpoints return 200 with normalized JSON in the same response.
Do you publish latency targets?
No. There is no public SLA or QPS figure.
Can Bing be queued?
No. Only the three Google verticals have /tasks.
Same price sync vs async?
Yes. Both are 2 Credits per completed search (display rate).
Results in the same response
Get an API key and call the sync endpoint for the engine you need.
Baidu and Ecosia endpoints opening soon.