Yandex API endpoint
Use Crawlora's Suggest Yandex search queries API to extract supported public Yandex data as structured JSON. This page includes request parameters, cURL examples, response schema, error behavior, credit cost, and a Playground link for testing before integration.
/yandex/suggestReturns Yandex search-box autocomplete completions for a query prefix, in Yandex's own ranking order. `lang` is the two-letter Yandex UI language (en, ru, tr, ...) and re-ranks the list; Yandex ignores codes it does not support. Developers commonly use this endpoint for data enrichment, monitoring, research dashboards, internal automation, and agent-native workflows that need repeatable structured public web data. Authentication uses the documented Crawlora headers, and usage is metered with the credit cost shown on this page.
Request parameters are generated from the active endpoint catalog. Required values must be sent before Crawlora can call the upstream public web data source.
| Parameter | Type | Required | Default | Description | Example |
|---|---|---|---|---|---|
| q | string | Yes | Search query prefix | openai | |
| count | integer | No | 10 | Suggestions to return; defaults to 10, clamped to 1..20 Minimum: 1. Maximum: 20. | 10 |
| lang | string | No | en | Two-letter Yandex UI language, such as en, ru, or tr; defaults to en | en |
| x-api-key (header) | string | Yes | API key required |
curl -X GET "https://api.crawlora.net/api/v1/yandex/suggest?q=openai&count=10&lang=en" \ -H "x-api-key: $CRAWLORA_API_KEY"
Send your scraping API key in the x-api-key header. Use the console API Keys page to rotate or select the active key.
Endpoint usage is metered in credits. The plan prices, included credits, limits, and overage rates below match the active backend billing configuration.
| Plan | Price | Included credits | Daily cap | Rate limit | Overage |
|---|---|---|---|---|---|
| Free | $0/mo | 2,000 | 500 daily credits | 5/min | No overage |
| Starter | $9/mo | 20,000 | 5,000 daily credits | 15/min | $0.75/1,000 overage credits when enabled |
| Growth | $29/mo | 100,000 | 25,000 daily credits | 45/min | $0.45/1,000 overage credits when enabled |
| Pro | $79/mo | 400,000 | No daily cap | 120/min | $0.30/1,000 overage credits |
| Business | $199/mo | 1,200,000 | No daily cap | 300/min | $0.20/1,000 overage credits |
| Enterprise | $499/mo | 5,000,000 | No daily cap | 1,000/min | $0.12/1,000 overage credits |
This endpoint is executed through Crawlora's managed scraping infrastructure.
- Yandex sometimes inlines answer rows (for example weather) in the list; those rows are reduced to their query text. - Yandex ignores a well-formed `lang` it does not support; only the format is validated here. - A prefix with no completions returns a valid empty `suggestions` array, not an error.
Crawlora does not silently return bad data when the upstream page cannot be used.
| Status | Common failure case |
|---|---|
| 400 | Invalid input or missing required parameter |
| 429 | Plan or endpoint rate limit exceeded |
| 500 | Internal execution error |
| 502 | Upstream platform failed, returned unusable HTML, or served a challenge page that could not be resolved |
When possible, Crawlora returns structured error context so your integration can retry, back off, or inspect the request.
| Status | Description | Schema |
|---|---|---|
| 400 | Missing or invalid parameters | #/definitions/app.Response |
| 429 | Rate limit exceeded | #/definitions/app.Response |
| 500 | Internal server error | #/definitions/app.Response |
| 503 | Yandex upstream request failed | #/definitions/app.Response |
{
"code": 200,
"msg": "OK",
"data": {
"query": "openai",
"suggestions": [
{
"position": 1,
"query": "openai"
},
{
"position": 2,
"query": "openai api"
},
{
"position": 3,
"query": "openai chatgpt"
}
]
}
}Request schema
No body schema
Response schema
#/definitions/yandex.suggestResponseDoc
| Field | Type | Required | Enum | Bounds | Example | Description |
|---|---|---|---|---|---|---|
| code | integer | No | 200 | |||
| data | suggest.Response | No | ||||
| data.query | string | No | openai | |||
| data.suggestions | array | No | ||||
| data.suggestions[].position | integer | No | 1 | |||
| data.suggestions[].query | string | No | openai api key | |||
| msg | string | No | OK |
Use environment variables for secrets and keep Crawlora API keys server-side.
curl -X GET "https://api.crawlora.net/api/v1/yandex/suggest?q=openai&count=10&lang=en" \
-H "x-api-key: $CRAWLORA_API_KEY"Crawlora is designed for responsible structured public web data workflows. Customers are responsible for using Crawlora in compliance with applicable laws, third-party rights, target-platform rules, and Crawlora terms.
Read Crawlora terms