Yandex Search Scraper

Yandex Search Scraper — Extracto API reference

Get structured Yandex search results for a query, region and result page.

Using Extracto

Extracto provides a web interface and HTTP API for submitting scraping tasks, tracking their status and retrieving structured results. Some parsers use third-party scraping providers for execution. Your Extracto account, API key and credit balance are managed at extracto.cloud.

Create an account at https://extracto.cloud/register, confirm your email and create an API key at https://extracto.cloud/api-keys. You can also configure and run this parser in the web interface at https://extracto.cloud/marketplace/yandex-search-scraper.

Pricing and credits

Current Extracto price: 75% of actual XMLProxy request cost · RUB converted to USD · fractional credits carried forward. Customer cost is 75% of the actual XMLProxy balance decrease attributable to this request, converted from RUB to USD using the official CBR rate saved for the task. There is no additional markup or minimum usage charge. The estimate temporarily reserves whole credits at the account maximum provider rate. Fractional credits accumulate between completed requests on your account and are deducted when they reach one full credit. An empty successful search can still have a provider cost; failed or cancelled tasks do not add a customer charge. Review the cost estimate in the web interface or POST your request body to https://extracto.cloud/api/v1/parsers/yandex-search-scraper/estimate before launching a task. An estimate does not start scraping. Credit packages are listed at https://extracto.cloud/pricing; billing details are at https://extracto.cloud/docs#billing.

Input

Send JSON with the parser settings inside an input object. The example is a starting point: replace the sources and limits with your own permitted targets. Launching it starts a real task and can spend credits.

{
    "input": {
        "query": "restaurants in Kyiv",
        "region": 143,
        "page": 0,
        "resultsPerPage": 10,
        "domain": "ru",
        "filter": "moderate"
    }
}

The provider may prepare a result asynchronously. Extracto checks the identical request again after five minutes, for up to 30 minutes. Pending checks reuse the provider request and do not create another Extracto task or credit reservation. Cancel the task in your account to stop further checks.

• query (string, required)
• region (integer, optional)
• page (integer, optional)
• resultsPerPage (integer, optional)
• domain (string, optional)
• filter (string, optional)

Requests and authentication

Use your Extracto key in the X-API-KEY header. Send Content-Type: application/json and Accept: application/json. Keep the key private on your server.

POST https://extracto.cloud/api/v1/parsers/yandex-search-scraper — submit a queued search (HTTP 202). This parser always uses the queue, including requests to the base endpoint. POST https://extracto.cloud/api/v1/parsers/yandex-search-scraper/queue — submit a queued task. Save run.id from the HTTP 202 response. GET https://extracto.cloud/api/v1/parser-runs/{run_id} — check a saved task using the same account's API key. Poll about once every five seconds while its status is queued or running. Stop at ok, partial, cancelled or error. Saved results are in run.result; failures are described in run.error.

Integration examples, response formats, errors and limits: https://extracto.cloud/docs.

Output

Returned fields depend on the parser, input and source availability. A successful task can return no matching records. Availability and completion time can change when the source website changes. The following sample is illustrative documentation data, not a customer run or a guarantee of results:

[
    {
        "query": "example search",
        "position": 1,
        "title": "Example result",
        "url": "https://example.com/result",
        "snippet": "Illustrative search snippet.",
        "domain": "example.com",
        "page": 0,
        "region": 0
    }
]

• query (string): The submitted search query.
• position (integer): Organic result position for the requested page.
• title (string): Search result title, with highlight markup removed.
• url (string): Result destination URL.
• snippet (string): Text passages returned by Yandex.
• domain (string): Result website domain.
• page (integer): Requested zero-based page number.
• region (integer): Requested Yandex region ID.

Example uses

• Research organic search results for a topic.
• Compare search results for selected regions.
• Export search result URLs and snippets for reporting.

Responsible use and support

Use this parser only for data you are permitted to access and process. Follow applicable laws, source website terms and Extracto's acceptable-use policy: https://extracto.cloud/acceptable-use. For help, email [email protected] and include the parser name and run ID. Never send your API key. Terms: https://extracto.cloud/terms Privacy: https://extracto.cloud/privacy Refund policy: https://extracto.cloud/refund-policy