Yandex API Documentation

First request

Endpoint

GET /yandex/search

Cost

3 credits/request

curl "https://api.crawlora.net/api/v1/yandex/search?q=openai" \
  -H "x-api-key: $CRAWLORA_API_KEY"

How to use Yandex endpoints

Yandex's current Webmaster documentation describes a crawler-built index and explains that indexed pages must be accessible to Yandex's crawler, while current Search support pages document region, language, date, and suggestion settings. Crawlora's /yandex/search contract returns normalized organic rows and excludes advertisements; /yandex/suggest returns ranked query completions. Web search accepts 1-based page values through 10 and localizes to the service egress region. Suggest accepts count through 20 and a two-letter UI language such as en, ru, or tr.

1. Step 1

   Query Yandex organic results

   GET /yandex/search with required q and optional page from 1 through 10. Each organic row carries position, title, URL, display_url, and description when Yandex shows a snippet.

2. Step 2

   Record the regional boundary

   Yandex localizes results to Crawlora's egress location, so the endpoint is unsuitable for claiming a caller-selected city or country. Record run time and observed market context when comparing rankings.

3. Step 3

   Follow result pagination

   Store pagination.page and follow pagination.next_page only when present. A page with neither organic rows nor a captcha marker is treated as parser drift and reported as an upstream failure, not a successful empty SERP.

4. Step 4

   Collect language-aware suggestions

   GET /yandex/suggest with q, count from 1 to 20, and a two-letter lang such as ru. Yandex may reduce inline answer rows to their query text and silently ignore a well-formed language code it does not support.

Other Search & Web Discovery APIs