# Eurostat House Price Index — Quarterly, Per Record (`nexgensignal/eurostat-house-price-index`) Actor

Official Eurostat quarterly House Price Index as per-record data. One row per observation — geography, quarter, dwelling type, unit, index value — verbatim from the source. No API key. Pay per record. Part of NexGen Signal — official-source data products.

- **URL**: https://apify.com/nexgensignal/eurostat-house-price-index.md
- **Developed by:** [NexGen Signal](https://apify.com/nexgensignal) (community)
- **Categories:** Real estate, Business, News
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $33.50 / 1,000 house price index records

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

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

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
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.
Actors are written with capital "A".

## 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.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## Eurostat House Price Index — Quarterly, Per Record

**Official source. No API key. Pay per record.**

This actor turns Eurostat's quarterly House Price Index (dataset `prc_hpi_q`) into clean, per-record data. Each run reads the index directly from Eurostat's public JSON-stat dissemination API, unpacks every observation into a single flat row, and delivers one record per data point — the geography, the period, the type of dwelling purchase, the unit, the index value, and Eurostat's own status flag, all reproduced exactly as Eurostat publishes them. You are billed only for records you actually receive. A blocked or failed run delivers nothing and charges nothing.

### What this is, in one paragraph

The House Price Index measures how the prices paid by households to buy residential dwellings change over time, expressed as an index (2015 = 100 for the standard index unit). This actor does not model, forecast, rescale, or reinterpret anything. It fetches the published figures, applies the licence-permitted geography filter (explained below), and hands you the numbers as rows you can load into a spreadsheet, a database, or a pipeline. If Eurostat says the value for Germany in 2024-Q1 is 148.99, that is exactly what lands in your dataset — same value, same unit, same flag.

### Who buys this and for what job

This is built for people who need the official European house-price series as data, not as a chart on a web page:

- **Analysts and researchers** comparing residential price trends across EU and EFTA markets without hand-copying figures out of Eurostat's browser.
- **Proptech, mortgage, and real-estate teams** that want the benchmark index feeding a model or dashboard on a repeatable schedule.
- **Data engineers** who want a keyless, one-call source of a well-known official series they can wire into an existing pipeline in minutes.
- **Journalists and policy teams** who need the underlying numbers behind a headline, with the exact period, unit, and provisional/break flags intact.

The job it does: get the official index, every geography and quarter, as rows — reliably, with provenance, and without an account or key at the source.

### Pricing

Pay per event. One event: a delivered house price index record. Tiered by your Apify plan; the record is delivered before it is charged.

| Event | What triggers it | Free plan | Bronze | Silver | Gold / Platinum / Diamond |
|-------|------------------|-----------|--------|--------|---------------------------|
| `house_price_record` | One delivered index observation | $0.05 | $0.045 | $0.04 | $0.0335 |

There is no start fee and no subscription. Blocked runs, source outages, and empty results cost nothing, because the charge only fires after a record is pushed to your dataset.

### Input

| Field | Type | Default | Description |
|-------|------|---------|-------------|
| `sinceTimePeriod` | string | `2024` | Earliest period to return. A year (`2024`) or a quarter (`2024-Q1`). An earlier start returns more history and more records. |
| `maxRecords` | integer | `500` | Ceiling on records delivered and billed this run. The default is a small, fast sample; raise it (up to 200,000) to pull the full set. |

Both fields are optional. The default run — `sinceTimePeriod = 2024`, `maxRecords = 500` — is a bounded sample that finishes in well under a minute so you can see the shape before you scale up.

### Output

One JSON object per observation. Values, units, dimension codes, and status flags are copied verbatim from Eurostat; a composite `record_id` (`freq:purchase:unit:geo:time`) uniquely identifies each row so no two source observations ever collapse together. Example record from a real run:

```json
{
  "record_id": "Q:TOTAL:I15_Q:DE:2024-Q1",
  "dataset_code": "prc_hpi_q",
  "indicator": "House price index",
  "freq": "Q",
  "freq_label": "Quarterly",
  "purchase": "TOTAL",
  "purchase_label": "Total",
  "unit": "I15_Q",
  "unit_label": "Index, 2015=100",
  "geo": "DE",
  "geo_label": "Germany",
  "time_period": "2024-Q1",
  "value": 158.9,
  "obs_status": null,
  "source": "Eurostat",
  "source_dataset": "prc_hpi_q",
  "licence": "Eurostat, CC BY 4.0. Reformatted from Eurostat JSON-stat; values unmodified. Third-party content and logos excluded. Commercial-barred geographies removed.",
  "attribution": "Source: Eurostat (dataset prc_hpi_q)",
  "caveat": "This is an index, not a price level, property valuation, or affordability measure. Where the unit is an index, the base is 2015=100. Values are reproduced verbatim from Eurostat.",
  "observed_at": "2026-08-17T00:00:00Z"
}
```

The `purchase` dimension distinguishes total dwellings from new versus existing dwellings, verbatim from Eurostat. The `unit` dimension distinguishes the index (2015 = 100), the quarterly and annual rates of change, and so on — again, verbatim. Where Eurostat attaches a status flag (for example `p` for provisional or `b` for a series break), it appears in `obs_status` unchanged.

Every run also writes an unbilled `RUN_RECEIPT` to the run's key-value store: the robots check result, the source URL, how many observations were present, how many were delivered, how many were excluded as missing or as commercial-barred geographies, and whether the number charged equals the number delivered.

### Cost guidance

A typical run bills one `house_price_record` per delivered observation, so the cost is simply the number of records you pull times your plan's per-record price. Pulling the full quarterly set from 2024 onward is roughly 3,700 records — about **$185** on the Free-plan rate, or about **$124** at the Gold-tier rate. A quick default sample of 500 records is about **$25** (Free) or **$16.75** (Gold). You control the volume with `sinceTimePeriod` and `maxRecords`.

### Honest limitations and caveats

- **It is an index, not a price.** The values are index numbers (2015 = 100 for the index unit) or rates of change — not house prices in euros, not valuations, and not an affordability measure. Do not read a value of 158.9 as a price.
- **Cadence.** The source is quarterly. Recent quarters are frequently marked provisional and are revised in later releases; because this is a living source, a value you pull today can change in a future Eurostat update. Pull again to refresh.
- **Coverage is licence-limited by design.** Eurostat permits commercial reuse only for EU, EFTA, and official EU acceding/candidate countries. Geographies outside that set (for example the United Kingdom, and non-European reporters) are excluded at ingest and counted in the run receipt. This is a deliberate compliance choice, not a data gap.
- **Missing observations are excluded, never invented.** Where Eurostat has no observation for a cell, no row is produced; the count of missing cells is reported in the receipt. Published zeros are kept as real values.
- **No person-level data.** This series is national/aggregate only. There is no individual, household, or address data in the source and none is ever constructed.
- **Partition.** One run pulls the whole permitted set for the chosen start period in a single call; there is no per-country partitioning needed at this size.

### The NexGen Signal family

Part of the NexGen Signal family of official-source, per-record Eurostat products. Its live siblings on the store — all official source, no API key, values verbatim, pay per record:

- [Eurostat Waste Generation](https://apify.com/nexgensignal/eurostat-waste-generation)
- [Eurostat Waste Treatment](https://apify.com/nexgensignal/eurostat-waste-treatment)
- [Eurostat Business & Consumer Confidence](https://apify.com/nexgensignal/eurostat-business-confidence)
- [Eurostat Income Distribution (EU-SILC)](https://apify.com/nexgensignal/eurostat-income-distribution)

*Source: Eurostat. Reformatted from the Eurostat JSON-stat dissemination API; values unmodified. Third-party content and logos are excluded. Data for geographies outside EU/EFTA/candidate countries is excluded in line with Eurostat's reuse terms.*

# Actor input Schema

## `sinceTimePeriod` (type: `string`):

Return observations from this period onward. Use a year (2024) or a quarter (2024-Q1). Earlier start = more records.

## `maxRecords` (type: `integer`):

Maximum records delivered and billed. You are billed only for records actually delivered. Raise it to pull the full set.

## Actor input object example

```json
{
  "sinceTimePeriod": "2024",
  "maxRecords": 500
}
```

# Actor output Schema

## `results` (type: `string`):

The delivered House price index records.

# 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 = {
    "sinceTimePeriod": "2024",
    "maxRecords": 500
};

// Run the Actor and wait for it to finish
const run = await client.actor("nexgensignal/eurostat-house-price-index").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 = {
    "sinceTimePeriod": "2024",
    "maxRecords": 500,
}

# Run the Actor and wait for it to finish
run = client.actor("nexgensignal/eurostat-house-price-index").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 '{
  "sinceTimePeriod": "2024",
  "maxRecords": 500
}' |
apify call nexgensignal/eurostat-house-price-index --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,nexgensignal/eurostat-house-price-index"
        }
    }
}

```

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/VEd3axdt2XNALO0dU/builds/lpGgTAwiDi79AGXYT/openapi.json