Subito.it Listing and Seller Data Through One API Call
Subito.it pages are built with JavaScript and watched by bot detection, so a plain fetch usually returns an empty shell or a challenge.
This integration puts a headless browser and rotating proxies behind a single HTTP request: you send a Subito.it URL, and you get back rendered HTML or structured JSON. The guide below covers what the scraper reads from a listing, which request parameters change the result, what each option costs in credits, and how the plan tiers differ.
What the API does with a Subito.it URL
You hand over a URL from Subito.it's listing pages. The service loads it in a real headless browser, runs the page's JavaScript, rotates proxies so the request resembles ordinary traffic, and returns the post-render HTML. If you would rather not parse HTML yourself, add extraction rules to receive structured JSON instead.
Most Subito.it collection work clusters around three questions, and each maps to a different slice of the listing page:
- Which categories are alive in which regions? Count new postings per category and region over a fixed window, then compare the counts week to week. The category and region fields carry this on their own; you do not need titles or descriptions.
- What is a fair asking price right now? Group asking prices by category and region, then track the median over time. This is the field that tells you whether a secondhand segment is heating up or cooling, and where a competitor's pricing sits relative to the local norm.
- What does the listing itself say? Category, region, posting date and the description text together support classifieds research — for example, dating when a category's listings start to mention a new model or season.
A deliberate boundary: inventory monitoring surfaces seller-listing patterns, not individual contact details. Plan your schema around public listing attributes rather than personal contact data.
Fields a listing page yields
Each Subito.it listing page returns the same core set: category, region, listing title, asking price, posting date, public seller handle and the image gallery. That set is enough for a price index, a category dashboard or a regional inventory count without any secondary scraping step.
Before you build, decide which of those fields your downstream system actually needs. If you only need price and region, a CSS extraction rule is cheaper to maintain than an AI extraction rule. If listing descriptions vary in structure across categories, natural-language extraction is the more forgiving option.
Choosing request parameters before you spend credits
The base call needs only the target URL. Everything else is optional and each option has a credit consequence, so choose deliberately:
- render_js=true runs the page in a headless browser and returns post-render HTML. Each successful request with JS rendering costs 5 API credits.
- stealth_proxy is the escalation path when a target turns aggressive. Premium proxies cost 10 credits per successful request with JS rendering disabled, or 25 with it enabled.
- country_code routes the request through a residential IP in that country. Geotargeting reaches 200+ countries and territories, or 40+ on classic proxies.
- extract_rules target exact elements with CSS or XPath selectors; ai_extract_rules describe the data you want in natural language.
A practical order of operations: start with the plain call, add render_js when the HTML comes back empty, add stealth_proxy only if you still see challenges, and add country_code only when the content genuinely varies by geography. Escalating in that order keeps credit spend proportional to the difficulty of the target.
A worked monitoring loop
Suppose you want to watch secondhand pricing for one category across two Italian regions. The loop is: build the Subito.it listing URL for the category and region, send it with render_js enabled, apply an extraction rule that keeps title, asking price, region and posting date, then store the rows with a run timestamp.
Run it on a schedule that matches how often listings actually change in that category, not on the shortest interval the API allows. Because the API enforces concurrency limits per plan rather than per-target rate limits, the constraint you will hit first is your own plan's simultaneous-request ceiling. If Subito.it itself starts throttling aggressive patterns, spacing requests out or splitting work across sessions is the fix — not buying more concurrency.
Plan tiers and what changes between them
The tier structure below is captured from the source page as a dated reference, not a live quote from this publisher. Confirm current pricing, inclusions and terms with the owner before relying on any figure. As captured, every tier lists JavaScript rendering, rotating and premium proxies, geotargeting, and screenshots with extraction rules; what separates the tiers is the monthly credit allowance and the number of concurrent requests. Priority email support, a dedicated account manager and team management appear only from the Business tier upward.
The comparison table reproduces the published tiers with their credit allowances and concurrency ceilings. Note also that, as captured, credits are valid for one month and do not roll over, and that requests start at 1 credit each before any rendering or proxy multiplier applies.
Getting from signup to a first response
Account creation is the first step: you receive an API key, and the starting credit balance depends on the allowance the operator sets for new accounts. From there, install the client library for your stack — Python, Node, Go, PHP or Ruby — or skip the SDK and issue a GET or POST request carrying the target URL directly. A request builder in the dashboard lets you paste a URL, adjust parameters and copy a generated snippet in Python, Node, Go, PHP, Ruby or cURL, which is handy for assembling a call before committing it to code. Code samples exist for every major language, and the documentation covers the parameter reference. The cheapest way to validate an extraction rule is a single listing page: confirm which fields it actually captures, then scale the same rule to a category.
Why the browser and proxy layer matters here
Subito.it depends on client-side rendering and active bot detection, which is exactly the combination that breaks naive scrapers. Rotating proxies avoid IP-based blocks, and headless browser rendering mimics ordinary browsing behaviour to lower the blocking risk further. The platform is built to run thousands of headless browsers and rotating proxies concurrently, so traffic spikes do not require you to provision anything.
Typical responses arrive within a few seconds, including on JavaScript-heavy pages. If a specific target still challenges requests, the stealth proxy option is the documented escalation rather than a rewrite of your client.
Data handling and compliance posture
How scraped data is stored and whether personal data is retained is a policy question each operator must answer for itself; the applicable GDPR and CCPA position should be stated explicitly in the service terms rather than assumed. For Subito.it work, the practical default is the same either way: seller handles are public listing attributes, while individual contact details sit outside the intended scope of inventory monitoring. Confirm your own lawful basis for processing any listing data you retain, and keep retention periods tied to the research or monitoring purpose.
Who this fits
This integration suits data analysts building regional price indices, growth teams watching a secondhand marketplace, developers who want a thin HTTP client instead of a browser fleet, and e-commerce businesses tracking resale positioning. It is not a lead-list generator: it returns listing attributes, and the seller handle is the public identifier you get.
| Plan | Monthly price | API credits | Concurrent requests | Priority email support | Account manager | Team management |
|---|---|---|---|---|---|---|
| Hobby | $19 /mo | 75,000 | 25 | Not included | Not included | Not included |
| Freelance | $49 /mo | 250,000 | 50 | Not included | Not included | Not included |
| Startup | $99 /mo | 1,000,000 | 100 | Not included | Not included | Not included |
| Business | $249 /mo | 3,000,000 | 200 | Included | Included | Included |
| Business + | $599 /mo | 8,000,000 | 400 | Included | Included | Included |
| Enterprise 14 | $999 /mo | 14,000,000 | 500 | Included | Included | Included |
| Enterprise 24 | $1,599 /mo | 24,000,000 | 600 | Included | Included | Included |
| Enterprise 41 | $2,399 /mo | 41,000,000 | 700 | Included | Included | Included |
| Enterprise 69 | $3,599 /mo | 69,000,000 | 800 | Included | Included | Included |
| Enterprise 120 | $5,799 /mo | 120,000,000 | 900 | Included | Included | Included |
Captured reference figures from the source page, not a live quote from this publisher. All prices are exclusive of VAT. As captured, every tier includes JavaScript rendering, rotating and premium proxies, geotargeting, and screenshots with extraction rules. Credits are valid for one month and do not roll over; requests start at 1 credit each, JS rendering costs 5 credits per successful request, and premium proxies cost 10 or 25 credits depending on whether JS rendering is enabled. Confirm current pricing, inclusions and terms with the owner before purchase.
Frequently asked questions
How do I make a first Subito.it request?
Register to get an API key, then send a GET request containing the Subito.it URL. The starting credit balance depends on the allowance the operator sets for new accounts. The service renders the page, rotates proxies and returns the result. A single listing page is the cheapest way to confirm your extraction rule before scaling to a category.
What should I do if Subito.it challenges my requests?
Requests already rotate residential proxies and use a real headless browser, so they resemble normal traffic. If a target becomes aggressive, switch on stealth_proxy for that request rather than rebuilding your client.
Can I test requests without writing code?
Yes. The dashboard request builder accepts a pasted URL and parameters, and generates a ready-to-copy snippet in Python, Node, Go, PHP, Ruby or cURL.
How is JavaScript handled on Subito.it pages?
Set render_js=true. The page runs in a real headless browser, the JavaScript executes server-side, and you receive the HTML as it appears after rendering.
Can I request Subito.it content as seen from a specific country?
Yes. Pass country_code to route through a residential IP in that country, which matters when listing content or availability varies by geography.
Is there a per-target rate limit?
No. Limits are concurrency ceilings tied to your plan, not per-target rates. If Subito.it throttles aggressive patterns, space requests out or split the work across sessions instead of assuming a higher tier will solve it.