# Casa.it Properties and Details Scraper (Authorization Required) (`realestateapi/casa-it-properties-and-details-scraper`) Actor

No-request Casa.it property Actor scaffold. Automated or manual source collection remains disabled pending separately documented, reviewed written authorization.

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

## Casa.it Properties and Details Scraper

CSV rank: **795**. Store listing: [skebby/casa-it-scraper](https://apify.com/skebby/casa-it-scraper).

### Current status

This Actor makes no Casa.it source requests and emits no new dataset records. Its runtime completes as `SUCCEEDED` / `SKIPPED_POLICY` with `requestCount: 0`. Casa.it's current Terms of Use require prior written consent for automated or manual access/copying of site information without authorization and restrict commercial or competitive reuse. No applicable written authorization is recorded. A checkbox or operator attestation cannot grant or verify permission.

The previous parser and record normalizer remain available for offline tests only. They are not called by the Actor entrypoint. The dataset contract allows source-backed property listings only; errors and permission skips never become dataset rows. The two historical blocked diagnostic rows were copied byte-for-byte to the external run-status archive and SHA-256 verified before removal from the active dataset. Their latest-run `OUTPUT_SUMMARY` was normalized to `FAILED` / `FAILED` with zero property items because the historical run returned only a challenge. No live run or source request was made.

### Local verification

```powershell
npm test
apify validate-schema
node --check src/main.js
node --check src/policy.js
```

These checks validate offline code, the listing-only dataset contract, the historical run summary, and schemas only. They do not establish authorization or live extraction.

### Dependency remediation — October 3, 2026

This Actor uses native HTTP and parser code, with a small readable default-storage adapter and the pinned official Apify logger. The unused SDK/crawler/proxy/cache dependency graph was removed because its current http-cache-semantics advisory has no released fix. Cloud storage uses the documented Apify REST interface and bearer headers; local writes append indexed JSON without overwriting historical rows. Storage failures propagate and ambiguous POST writes are not retried. Native exit codes and source authorization/access gates are preserved. Node 22.19+ is required. The source remains unqualified until its existing permission/access prerequisites are met.

Relevant advisory: https://github.com/advisories/GHSA-ch52-4w7c-c8xp. Runtime regression checks: node --test test/platform.test.js.

# Actor input Schema

## Actor input object example

```json
{}
```

# 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/casa-it-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/casa-it-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/casa-it-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/casa-it-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/lX5nuCNdERkEx47EZ/builds/cXalcfCjtJGvGouxT/openapi.json