# Astegiudiziarie Properties and Details Scraper (`realestateapi/astegiudiziarie-properties-and-details-scraper`) Actor

AsteGiudiziarie Italy no-request policy scaffold. Current Conditions of Use prohibit automated mass retrieval of detailed sale documents and protect the auction database.

- **URL**: https://apify.com/realestateapi/astegiudiziarie-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

## Astegiudiziarie Properties and Details Scraper

This Actor is currently a no-request policy scaffold. Aste Giudiziarie Inlinea’s [Conditions of Use](https://www.astegiudiziarie.it/condizioni-generali) were checked in Chrome on 2026-09-26. Article 4 limits access and downloads to personal, non-commercial use and prohibits automated tools for mass retrieval of documents from detailed sale records. Article 5 requires express authorization for copying protected content, and Article 6 protects the auction database and warns against extraction or reuse.

Default runs finish with `status: SUCCEEDED` and `runStatus: SKIPPED_POLICY`, zero source requests, and no dataset rows. A clean collection uses `runStatus: COMPLETED`, a partial collection uses `PARTIAL`, and a failure uses `FAILED`; top-level status remains `SUCCEEDED` when the run completed or saved real rows before a later failure. New failed KVS summaries include a stable `failureCode` and generic `failureReason`; no diagnostic rows are written. The authorization checkbox is an operator attestation only; it does not grant or verify permission and never enables requests. An attested run also remains a successful policy skip.

Eight historical source-backed auction rows remain preserved. The existing `OUTPUT` summary reports `status: SUCCEEDED` and `runStatus: COMPLETED` for its historical three-item run; new summaries use the same outcome-specific `runStatus` mapping. The rows are not verified as current or authorized for reuse. Offline parser tests use synthetic HTML only and do not establish live source coverage. Validation and runtime failures produce a `FAILED` summary and no diagnostic dataset rows.

```sh
npm test
npm run check
apify validate-schema
```

### Runtime dependency remediation

Batch input and JSON storage use the documented Apify REST API and isolated local JSON storage, with environment-only credentials, bounded requests, no platform redirects, and no automatic dataset-POST retry. The Actor does not import the full Apify/Crawlee SDK. Source collection rules and authorization gates are unchanged. This adapter does not provide request queues, proxies, browser automation, encrypted input fields, or long-running system-event migration. Those capabilities are not used by this implementation.

# Actor input Schema

## `authorizationConfirmed` (type: `boolean`):

Operator attestation only; it does not grant or verify permission. This Actor currently makes zero source requests, even when checked.

## `authorizationReference` (type: `string`):

Internal reference for applicable express authorization. Required with the attestation; not independently verified by this Actor.

## Actor input object example

```json
{
  "authorizationConfirmed": false
}
```

# Actor output Schema

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

No description

## `output` (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/astegiudiziarie-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/astegiudiziarie-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/astegiudiziarie-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/astegiudiziarie-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/eJjrKYoWFAb4F5MKR/builds/MfGZPkr3RqQBDIDgq/openapi.json