Avito Properties and Details Scraper
Pricing
from $3.99 / 1,000 results
Avito Properties and Details Scraper
Bounded Avito real-estate listings parser. Source requests default to off pending current access and source-use verification; no live records are saved.
Pricing
from $3.99 / 1,000 results
Rating
0.0
(0)
Developer
Real Estate API
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
4 days ago
Last modified
Categories
Share
Review status
This folder contains an extractor intended for public Avito real-estate listing pages. Current source access and field coverage have not been verified. Generated searches are restricted to the /nedvizhimost category.
Chrome's browser safety policy rejected navigation to the configured Moscow real-estate search URL during the September 23, 2026 review. The actor-local review instructions prohibit retrying through another browser, HTTP client, proxy, or indirect route. No target page was accessible for field comparison. The saved OUTPUT_SUMMARY.json reports FAILED, one attempted page, and zero successful items; there are no saved dataset rows. The declared dataset fields and offline HTML fixture do not establish live extraction coverage.
Inputs
The input schema accepts an official Avito real-estate search URL, official listing URLs or numeric IDs, or a query and location. It also defines price, sort, result-limit, and optional-detail controls. These are implementation inputs, not verified source behavior. sourceAccessConfirmed defaults to false and makes the Actor skip with zero requests until Chrome navigation and the applicable source-use terms have been checked. The attestation does not grant permission.
Output contract
The dataset schema describes possible listing fields such as title, price, currency, images, seller name, location, attributes, ratings, and badges. No live Avito output is currently available to confirm which fields are actually emitted. The prior iPhone example has been removed because this folder's stated task is real-estate review and the example was not source-verified.
OUTPUT_SUMMARY.status is SUCCEEDED or FAILED; runStatus and collectionStatus are COMPLETED, PARTIAL, FAILED, or SKIPPED_POLICY. Counts and bounded failureReasons describe the current run. Successful explicit empty results complete without a dataset row. An unrecognized page or a failure with zero saved listings fails; access restrictions and redirects stop later requests. If real listing rows were saved before a later failure, the run remains SUCCEEDED/PARTIAL. Failures do not create diagnostic or placeholder records.
Access and safety
Do not run live collection until Chrome permits access under the actor-local review instructions and source-use terms are checked. Do not use another browser, HTTP client, proxy, indirect route, user-agent impersonation, or challenge interaction to get around the block. The Actor's HTTP client does not send a Chrome User-Agent and refuses redirects. Do not describe this Actor as working or copy listing values from fixtures.
Offline checks
npm test, npm run check, and apify validate-schema check the parser fixture, syntax, and Actor schemas only; they do not verify live extraction.
Runtime security and HTTP caching
The October 3, 2026 dependency remediation updates compatible runtime packages and uses patched basic-ftp 6.2.1. The unpatched http-cache-semantics dependency is explicitly replaced by the independently authored adapter in vendor/no-cache-policy. This disables HTTP response caching and cached-response revalidation, including reuse of old cached bodies or cookies. It is not an upstream security patch or a renamed upstream version. Requests always reach the origin; source gates and finite request limits still apply. Offline integration tests exercise real got caching and the get-uri FTP interface. See the adapter README for its interface and limitations.
