Scrape Yad2 Classifieds With One API Request
A Yad2 URL is the only input a managed scraping API needs to return rendered HTML, structured JSON, or Markdown.
Most pipelines built on it serve one of three ends: comparing rental prices across Israeli regions, collecting listing photos, or watching how listings age — re-posts, price cuts, and time on market. This page covers the fields a request returns, the parameters that change the response, how credits stack when features combine, and the checks to complete before you point a pipeline at production.
What a Yad2 request returns
Give the API a Yad2 URL and it renders the page, rotates proxies, and hands back rendered HTML or structured JSON. The documented listing fields are category, listing title, asking price, region, posting date, public seller handle, and the full image gallery. You can also ask for Markdown to feed an LLM, or capture a full-page screenshot for visual verification. No Yad2 account is needed — only a key from the scraping service.
Field map: what each Yad2 field is for
Use this map to decide which fields your pipeline actually needs before you write extraction rules.
Request inputs that change the output
A basic request is a GET with your API key and a Yad2 URL. Optional parameters tune the response: render_js enables JavaScript rendering for dynamic pages; stealth_proxy adds a stealth proxy for CAPTCHA-heavy targets; country_code routes the request through a specific country; ai_extract_rules accepts a natural-language spec and returns structured JSON without CSS selectors; extract_rules uses CSS or XPath selectors when you want precise control. The dashboard request builder generates a copy-ready snippet in Python, Node, Go, PHP, Ruby, or cURL if you prefer not to hand-write the call.
How credits are consumed
Credits are charged per successful request, and the total depends on which features you enable. The published tooltip constants are: base requests start at 1 credit each; JavaScript rendering adds 5 credits per successful request; Premium proxies cost 10 credits without JS rendering or 25 with it. How long credits stay valid and whether they roll over are set by the account terms you agree to, so check those before you size a batch. Plan tiers bundle credits with concurrency limits — see the plan table below for the current figures. VAT treatment follows the plan terms shown at checkout.
Worked example: cost of a JS-rendered Yad2 pull
Suppose you need 1,000 Yad2 listing pages rendered with JavaScript and routed through Premium proxies. The published constant for that combination is 25 credits per successful request — a single combined rate, not 10 plus 5. The batch therefore costs 25,000 credits. If you keep JavaScript rendering but drop Premium proxies, each request costs 5 credits and the same batch costs 5,000 credits. These figures use the published tooltip constants; confirm current rates on the pricing page before committing to a plan.
Decision checklist before you deploy
Use this checklist to decide whether a managed API fits your Yad2 workflow, and to catch the failure modes that are easy to miss.
Blocked vs. prohibited vs. post-login
These three failure modes look similar in logs but require different responses. A blocked request means the target served a challenge or rate-limited you — the fix is to enable stealth_proxy or slow the request rate. A prohibited request means the target's terms of service forbid the access you are attempting — the fix is to change scope or stop, not to add more proxies. Post-login content is out of scope for this API entirely; only public-facing pages are supported. Review the target site's terms of service before deploying, and avoid post-login content.
Legal and compliance checks
Public-facing pages can usually be scraped, but the operator of the target site sets the rules. Before you deploy, read Yad2's terms of service and confirm that the fields you plan to collect are permitted. How your own project handles and stores scraped data is a policy decision for your team, not something this page can certify. If your workflow touches seller contact data, treat that as a separate legal review — the documented Yad2 field set deliberately stops at the public seller handle.
Where the output can go
The API returns HTML, JSON, or Markdown, so the output can feed a database, an LLM pipeline, or a no-code workflow. For teams that prefer visual automation, an n8n integration lets you build listing and price-monitoring flows without writing scraper code. A JavaScript scenario option lets you click, scroll, wait for dynamic content, or run custom JS before the page is captured, which is useful when Yad2 listings load lazily.
| Field | What it tells you | Typical use |
|---|---|---|
| Category | The classifieds section the listing belongs to | Segment rental vs. sale vs. other categories |
| Listing title | The seller's headline text | Keyword filtering and deduplication |
| Asking price | The price the seller posted | Price tracking and regional comparisons |
| Region | The Israeli region the listing targets | Rental-market intelligence by area |
| Posting date | When the listing went live | Freshness and time-on-market signals |
| Public seller handle | The public identifier shown on the listing | Grouping listings by seller without collecting contact data |
| Image gallery | All listing photos | Visual research and listing-quality checks |
Field availability depends on what renders on the public page; post-login content is out of scope.
| Feature | Credits per successful request | Notes |
|---|---|---|
| Base request | 1 | Requests start at 1 credit each |
| JavaScript rendering | 5 | Added when render_js is enabled |
| Premium proxies (no JS rendering) | 10 | Added when Premium proxies are enabled |
| Premium proxies (with JS rendering) | 25 | Combined cost when both features are enabled |
Constants are the published tooltip values; how long credits stay valid and whether they roll over are set by the account terms you agree to. Confirm current rates on the pricing page.
| Check | Why it matters | Action |
|---|---|---|
| Target pages are public | Post-login content is out of scope | Confirm the URL resolves without a session |
| Terms of service reviewed | Public scraping is not automatically permitted | Read Yad2's ToS and record the decision |
| Fields limited to public data | Seller contact data needs separate review | Stop at the public seller handle |
| Blocking strategy chosen | Challenges and rate limits look like failures | Enable stealth_proxy or throttle requests |
| Credit budget modeled | JS rendering and Premium proxies multiply cost | Multiply request count by the per-request credit cost |
| Concurrency fits the plan | Plan tiers cap simultaneous requests | Match concurrency to the plan's limit |
Checklist items reflect documented behavior; plan limits and credit constants should be re-confirmed against current pricing.
Frequently asked questions
Do I need a Yad2 account to scrape listings?
No. You need a key from the scraping service, not a Yad2 login. The service sends the URL, handles proxies and rendering, and returns the response. The documented scope is public-facing pages only.
Is scraping Yad2 legal?
Public-facing pages can usually be scraped, but the target site's terms of service govern what is permitted. Review those terms before deploying, and avoid post-login content. This page is not legal advice.
What data can I extract from a Yad2 listing?
Anything that renders on the public page. The documented field set is category, listing title, asking price, region, posting date, public seller handle, and image gallery. Use extract_rules with CSS or XPath selectors for precise control, or ai_extract_rules for natural-language extraction that returns structured JSON.
How do I start scraping Yad2?
Create an account to get an API key, then send a GET request with the target Yad2 URL. The service renders the page, rotates proxies, and returns the data. The dashboard request builder generates a copy-ready snippet in Python, Node, Go, PHP, Ruby, or cURL if you prefer not to hand-write the call.
Will I get blocked when scraping Yad2?
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. A block is a challenge or rate limit; it is not the same as a terms-of-service prohibition.
Can I scrape Yad2 without writing code?
Yes. The dashboard request builder lets you paste a URL, set parameters, and copy the generated snippet in Python, Node, Go, PHP, Ruby, or cURL. For visual automation, an n8n integration lets you build listing and price-monitoring flows without writing scraper code.
How many credits does a Yad2 request cost?
Base requests start at 1 credit each. JavaScript rendering adds 5 credits per successful request. Premium proxies cost 10 credits without JS rendering or 25 with it — the 25 figure is the combined rate for both features, not an additional 10 plus 5. How long credits stay valid and whether they roll over are set by the account terms you agree to, so check those before you size a batch. Confirm current rates on the pricing page.
Can I track price drops and re-posts on Yad2?
Yes. The posting date field lets you compute time on market, and repeated pulls of the same listing let you detect price changes and re-postings. The documented workflow is to monitor listings for re-postings, price drops, and time on market without scraping seller contact data.