# Avito Properties and Details Scraper (`realestateapi/avito-properties-and-details-scraper`) Actor

Bounded Avito real-estate listings parser. Source requests default to off pending current access and source-use verification; no live records are saved.

- **URL**: https://apify.com/realestateapi/avito-properties-and-details-scraper.md
- **Developed by:** [Real Estate API](https://apify.com/realestateapi) (community)
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $3.99 / 1,000 results

This Actor is paid per event and usage. You are charged both the fixed price for specific events and for Apify platform usage.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## Avito Properties and Details Scraper

### 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.

# Actor input Schema

## `sourceAccessConfirmed` (type: `boolean`):

Set true only after Chrome permits the target and applicable source terms authorize the intended collection and storage. This attestation is not a permission grant; the default is zero requests.

## `searchUrl` (type: `string`):

Optional official HTTPS Avito real-estate search URL containing the /nedvizhimost category path. It takes priority over query and location.

## `listingUrls` (type: `array`):

Optional direct Avito listing URLs or numeric listing IDs for batch detail extraction.

## `query` (type: `string`):

Keywords used when searchUrl and listingUrls are omitted.

## `location` (type: `string`):

Avito city or region, for example Москва or Санкт-Петербург.

## `category` (type: `string`):

The generated search is restricted to Avito real estate.

## `priceMin` (type: `integer`):

Optional lower price filter for a generated search URL.

## `priceMax` (type: `integer`):

Optional upper price filter for a generated search URL.

## `sort` (type: `string`):

Ordering hint for a generated public search URL.

## `maxResults` (type: `integer`):

Maximum unique listing records to store.

## `includePhone` (type: `boolean`):

Keep a phone number only when the seller has exposed it on the public page.

## `includeDetails` (type: `boolean`):

Keep descriptions, images, location, and specification fields found on the public page.

## `includeReviews` (type: `boolean`):

Keep public rating and review counts when present.

## Actor input object example

```json
{
  "sourceAccessConfirmed": false,
  "location": "Россия",
  "category": "nedvizhimost",
  "sort": "relevance",
  "maxResults": 100,
  "includePhone": false,
  "includeDetails": false,
  "includeReviews": false
}
```

# Actor output Schema

## `dataset` (type: `string`):

No description

## `runSummary` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {};

// Run the Actor and wait for it to finish
const run = await client.actor("realestateapi/avito-properties-and-details-scraper").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {}

# Run the Actor and wait for it to finish
run = client.actor("realestateapi/avito-properties-and-details-scraper").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{}' |
apify call realestateapi/avito-properties-and-details-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,realestateapi/avito-properties-and-details-scraper"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/72pYskseQ9bjPCvdh/builds/msRytAXtqRxYyzlUT/openapi.json