How to Scrape Subito Listings with an API
Subito’s terms prohibit automated scraping. Learn what access is documented, which official workflows work, and how to request an approved data route.
Short answer: Do not build a scraper for Subito listings. The public documentation reviewed for this guide does not document a listings-search API, and Subito’s published terms prohibit automated access and extraction with robots, spiders, scrapers, or similar tools. If you need bulk marketplace data, request written authorization and a documented access route from Subito before writing code.
The right workflow depends on whose listings you need and what you are trying to achieve:
| Goal | Supported workflow documented by Subito | What it is not |
|---|---|---|
| Know when new ads matching your criteria appear | Save a search and enable notifications in your Subito account. | A listings API or bulk export. |
| Publish or manage your own inventory | Use MultiGestionale or an authorized third-party listing manager. | Permission to read other sellers’ ads. |
| Retrieve marketplace listings in bulk | Ask Subito for written authorization and an approved interface. | A reason to reverse-engineer app traffic, bypass controls, rotate identities, or use proxies. |
What Subito’s terms say
Subito’s general terms contain this sentence:
“Resta infine inteso che ogni eventuale utilizzo di robot, spider, scraper e/o ulteriori strumenti automatici per accedere al sito e/o per estrapolare i relativi dati, contenuti, informazioni è espressamente vietato.”
Translation for convenience: use of robots, spiders, scrapers, or other automated tools to access the site or extract its data, content, or information is expressly prohibited. The translation is not Subito’s exact wording. Review the current Subito terms before planning an integration because platform rules can change.
The same terms also restrict unapproved automated listing-management software for posting. That seller-side rule is separate from the anti-scraping clause: an authorized tool for uploading your own offers does not establish access to other users’ listings.
First, identify the data workflow you actually need
1. Monitoring new listings as a buyer
If your objective is “tell me when a listing matching these filters is published,” use Subito’s saved-search feature and account notifications. This is the official user workflow for alerts and does not require an automated client.
- Sign in to Subito.
- Set the category, location, price range, and other filters you need.
- Save the search.
- Enable the available email or push notifications.
- Review each result through Subito’s normal interface.
This approach is appropriate for human monitoring. It does not provide a machine-readable feed, historical export, guaranteed delivery schedule, or API credentials.
2. Importing your own stock as a professional seller
Subito documents MultiGestionale and authorized partner listing managers for importing and managing a seller’s own offers. Confirm that a provider is currently authorized and that its contract covers your account before sending inventory.
Expect a seller-management workflow: your system supplies records that you own, the manager publishes or updates those offers, and status is handled through the authorized integration. These materials are not evidence of a search endpoint for harvesting public ads.
3. Bulk access to marketplace listings
If you need fields such as title, price, publication date, URL, seller information, or category across many ads, contact Subito first. Ask for:
- written permission for your exact use case and fields;
- the approved delivery method (API, export, feed, or another interface);
- authentication and account requirements;
- rate, retention, and redistribution limits;
- deletion, privacy, and attribution requirements; and
- a technical contact and change-notification process.
The reviewed public materials do not establish whether Subito offers a private arrangement for this use case. Do not invent an endpoint, schema, API key process, or rate limit until Subito supplies it in writing.
What not to build
- Do not crawl listing pages with a bot, browser automation, or a scraping library.
- Do not reverse-engineer undocumented mobile or web endpoints.
- Do not evade CAPTCHA, bot checks, login controls, robots directives, or rate limits.
- Do not rotate proxies, identities, cookies, or user agents to conceal automated access.
- Do not republish or sell extracted listings without explicit permission and a lawful data basis.
These techniques would conflict with the published terms and can create account, contractual, privacy, and operational problems. This guide is not a legal opinion about how any law applies to a particular project.
Or skip the browser setup
ScreenshotNeo is a website screenshot API, not a Subito listings API. Use it only for pages you are authorized to access, such as your own site, a staging environment, or a Subito workflow covered by written permission. It returns a PNG, JPEG, WebP, or PDF from one GET request. See the ScreenshotNeo API documentation.
curl -G "https://api.screenshotneo.com/v1/shot" \\
-d access_key=YOUR_API_KEY \\
--data-urlencode url=https://www.subito.it \\
-o shot.webpimport requests
r = requests.get(
"https://api.screenshotneo.com/v1/shot",
params={"access_key": "YOUR_API_KEY", "url": "https://www.subito.it"},
timeout=90,
)
r.raise_for_status()
open("shot.webp", "wb").write(r.content)const q = new URLSearchParams({
access_key: 'YOUR_API_KEY',
url: 'https://www.subito.it'
});
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);
if (!res.ok) throw new Error(`HTTP ${res.status}`);
const image = Buffer.from(await res.arrayBuffer());
require('fs').writeFileSync('shot.webp', image);Before the capture, ScreenshotNeo can accept cookie or consent banners and remove more than 60 known consent platforms, newsletter popups, and chat widgets; each step can be disabled. Bot checks, blank pages, timeouts, failed loads, and cache hits are not billed, and the response identifies the result with X-Page-Verdict and X-Billed headers. Its MCP server provides take_screenshot, get_page_info, and capture_pdf tools for Claude, Cursor, and other MCP clients.
There are 1,000 screenshots per month on the free plan with no card. Paid plans start at $5 for 3,000 shots; every feature is available on every plan. Create a free ScreenshotNeo account.
Designing an approved integration
If Subito grants access, document the agreement before implementation. Keep the integration narrow and auditable:
- Store the written authorization, endpoint documentation, and permitted fields with the project.
- Implement the supplied authentication exactly; never guess tokens or scrape browser sessions.
- Honor the specified rate limits, pagination rules, caching limits, and deletion requests.
- Validate response schemas and fail closed when fields or permissions change.
- Log request IDs and status codes without storing unnecessary personal data.
- Provide a kill switch so access stops immediately if authorization expires.
Troubleshooting
| Symptom | Likely cause | Fix |
|---|---|---|
| There is no API key or developer endpoint | No public listings API is documented. | Use saved-search alerts for personal monitoring or request an approved route from Subito. |
| A MultiGestionale partner cannot return other sellers’ ads | Seller tools manage the account owner’s inventory. | Confirm ownership and scope; request separate marketplace-data authorization. |
| Your account is challenged or blocked | Automated access may violate the terms or trigger controls. | Stop automation and contact Subito; do not evade the control. |
| A page screenshot is blank or shows a consent dialog | The page requires consent, is blocked, or failed to load. | For an authorized page, inspect X-Page-Verdict, check the URL and permissions, and configure consent handling or waits in ScreenshotNeo. |
| A ScreenshotNeo response is not billed | The result may be a bot check, blank page, timeout, failed load, or cache hit. | Read X-Page-Verdict and X-Billed; correct the authorized target or reuse the cached result. |
Performance, reliability, and cost
- Prefer alerts for alerts. Saved searches avoid polling and are the documented way to learn about new ads.
- Keep approved requests bounded. Use the smallest field set, page only as authorized, and cache according to the agreement.
- Handle change. Treat undocumented HTML or app traffic as unstable and unsupported.
- For screenshots, choose the right mode. ScreenshotNeo supports full-page capture, CSS-element capture, waits, custom headers and cookies, blocking rules, device presets, PDF output, caching with a chosen TTL, asynchronous jobs, bulk capture of up to 100 URLs per call, and signed webhooks.
- Budget predictable work. ScreenshotNeo bills clean shots only; failed loads and cache hits do not consume a paid shot. The free plan includes 1,000 shots monthly, with paid plans from $5 for 3,000.
FAQ
Does Subito have a public listings-search API?
No public listings API was found in the documentation reviewed for this guide. That does not prove that no private agreement exists; ask Subito directly.
Can I use a seller integration to read competitors’ listings?
No. The documented integrations are for importing and managing a professional seller’s own offers.
Are saved-search notifications an API?
No. They are an account feature for human monitoring and alerts.
Can ScreenshotNeo extract listing data for me?
No. It captures an authorized webpage as an image or PDF. It is not a Subito data API and does not grant permission to automate access.
What should I send Subito when requesting access?
Describe your purpose, fields, volume, retention, users, security controls, and redistribution plans, and ask for written permission plus the technical documentation for the approved route.
