Skip to content

Yandex Images API

Yandex Images results are rendered by JavaScript and protected by bot detection, so a plain HTTP request often returns an incomplete page.

OUTPUT FORMATSHTMLJSONMarkdown

This API takes a Yandex Images URL, runs it in a real browser with rotating residential proxies, and returns the rendered result so your code can extract image metadata, duplicate signals, or classification labels.

What a Yandex Images request can return

A Yandex Images SERP exposes several kinds of data per result. The API returns the rendered page, and you can use extraction rules to pull the fields you need. The useful fields are image URL, thumbnail URL, source page, dimensions, classification tags, alt text, and SERP position. The same page can also carry ad placements and SERP-feature appearances, which the API can return as structured JSON when you request them.

Three workflows this API supports

Image research: pull results and metadata for a query, including the source page and dimensions, to study what visual content appears for a topic in Russian-language markets. Duplicate detection: compare image URLs or perceptual hashes across SERPs to find reused assets, which is useful for brand protection and content monitoring. Object and label extraction: read classification tags, object labels, and visual categories per image to support trend analysis or content research.

How a request works

Create an account to get an API key and free test credits. Install a client library for Python, Node, Go, PHP, or Ruby if you want one, or send a GET request directly. The request includes the Yandex Images URL and your API key. The renderer executes the page in a real browser, rotates the IP, and returns the response. For harder pages, add render_js to force JavaScript rendering, stealth_proxy to reduce CAPTCHA blocking, country_code to set geotargeting, and ai_extract_rules to describe the output you want in natural language instead of writing selectors.

Choosing request options: a short checklist

Start with the simplest request that returns the data you need, then add options only when the response shows a problem. Use render_js when the image grid or metadata is missing from the raw HTML. Add stealth_proxy when the target returns CAPTCHA or block pages despite rendering. Use country_code when the Yandex result set changes by region and you need a specific market view. Use ai_extract_rules when you want structured JSON but do not want to maintain CSS or XPath selectors. Each option changes the credit cost, so check the credit table before scaling a job.

Worked credit example

Suppose you send one Yandex Images URL with JavaScript rendering enabled and no premium or stealth proxy. The request costs 5 credits. If you add a premium proxy with JavaScript rendering, the same request costs 25 credits. If you use stealth_proxy, it costs 75 credits. A 75,000-credit Hobby plan therefore covers 15,000 requests at the 5-credit rate, but only 1,000 requests at the 75-credit rate. Run a small batch at the option level you expect to use before committing to a monthly volume.

URL matching versus perceptual hash

Matching by URL is exact and cheap: the same file address appears in multiple SERPs, so a URL set difference finds direct reuse. A perceptual hash compares visual similarity, so it can catch resized, recompressed, or slightly cropped copies that have different URLs. Use URL matching for a quick first pass and perceptual hashing when you need to find modified copies. Both approaches rely on the image results returned for your query, so choose query terms that cover the markets and languages you care about.

Output formats beyond raw HTML

The API can return the rendered page, structured JSON from extraction rules, a full-page screenshot, or a Markdown version of the page with embedded image references. Markdown output is useful when you want to pass image result pages to a language model without writing an HTML parser. Screenshots are useful when you need to see how the page actually renders in a browser. JavaScript scenarios let you click, scroll, wait for dynamic content, or run custom JavaScript before extraction.

Matching a plan to your request volume

The plan table below lists the captured monthly price, API credit allowance, concurrent request limit, and feature availability for each tier. The credit cost per request depends on the options you enable, so compare plans by the number of requests you expect at your actual option level, not by the headline credit count alone. All prices are exclusive of VAT. The free trial provides 1,000 credits with no credit card required, which is enough to test a small Yandex Images batch before choosing a paid tier.

Plan comparison
PlanPriceAPI creditsConcurrent requestsJavaScript renderingRotating & premium proxiesGeotargetingScreenshots & extraction rulesPriority email supportDedicated account managerTeam management
Hobby$19 /mo75,00025IncludedIncludedIncludedIncludedNot includedNot includedNot included
Freelance$49 /mo250,00050IncludedIncludedIncludedIncludedNot includedNot includedNot included
Startup (Recommended)$99 /mo1,000,000100IncludedIncludedIncludedIncludedNot includedNot includedNot included
Business$249 /mo3,000,000200IncludedIncludedIncludedIncludedIncludedIncludedIncluded
Business +$599 /mo8,000,000400IncludedIncludedIncludedIncludedIncludedIncludedIncluded
Enterprise 14$999 /mo14,000,000500IncludedIncludedIncludedIncludedIncludedIncludedIncluded
Enterprise 24$1,599 /mo24,000,000600IncludedIncludedIncludedIncludedIncludedIncludedIncluded
Enterprise 41 (Recommended)$2,399 /mo41,000,000700IncludedIncludedIncludedIncludedIncludedIncludedIncluded
Enterprise 69$3,599 /mo69,000,000800IncludedIncludedIncludedIncludedIncludedIncludedIncluded
Enterprise 120$5,799 /mo120,000,000900IncludedIncludedIncludedIncludedIncludedIncludedIncluded

Prices are exclusive of VAT. Credit allowances are monthly and do not roll over. Per-request credit cost depends on options: 5 credits for JavaScript rendering, 25 for premium proxy with JavaScript rendering, 75 for stealth_proxy.

Frequently asked questions

Do I need a Yandex account to scrape Yandex Images?

No. You need an API key for this service, not a Yandex account. Sign up, get the key and free test credits, then send the Yandex Images URL as a request parameter.

Is scraping Yandex Images legal?

Public-facing pages can usually be scraped, but review the target site's terms of service before deploying and avoid post-login content. Legal rules vary by jurisdiction and by the specific data you collect.

What data can I extract from Yandex Images?

Whatever is visible on the public page is fair game. To receive structured JSON, either target elements with extract_rules and CSS selectors, or hand the job to ai_extract_rules for AI-driven extraction. Common fields include image URL, thumbnail, source page, dimensions, classification tags, alt text, and SERP position.

How do I start scraping Yandex Images?

Sign up, grab your API key, and send a GET request with the target URL. The service renders the page, rotates proxies, and returns the data. Free test credits are included.

Will I get blocked when scraping Yandex Images?

The service rotates residential proxies and uses a real headless browser so requests resemble normal traffic. If a target becomes aggressive, enable stealth_proxy on the request.

How much does it cost to scrape Yandex Images?

Free test credits are available on signup with no card required. Paid plans start at $19/month for higher volume and concurrency. Credit cost per request depends on options: 5 credits for JavaScript rendering, 25 for premium_proxy with JavaScript rendering, 75 for stealth_proxy.