# EPC Properties and Details Scraper (`realestateapi/epc-properties-and-details-scraper`) Actor

EPC Properties and Details Scraper — Reads official UK energy certificate pages only after applicable reuse rights and a lawful basis for any personal data are confirmed. Requests and detail-page fetching are disabled by default.

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

## EPC Properties and Details Scraper

The official UK Find an energy certificate service is available in Chrome. GOV.UK's terms say most content is under the Open Government Licence, while that licence explicitly excludes personal data and certain third-party rights. The EPC service pages reviewed here did not identify a separate licence for address-level certificate records, so this Actor makes no source request unless you confirm the requested data is covered by applicable reuse rights and you have a lawful basis for any personal data. This default-off confirmation is an attestation; it does not grant rights.

When enabled with appropriate rights, the Actor can discover certificate URLs by postcode and parse certificate details such as address, current/potential ratings, expiry status, floor area, energy/emissions metrics, and recommended improvements. Certificate detail fetching is separately off by default. Search results can include expired certificates; each detail record identifies expiry when the official page exposes it.

### Local development

Run the deterministic parser, status, and rights-gate checks with `npm test`, then validate the schemas with `apify validate-schema` and saved local rows with `npm run validate`.

The dataset contains only real certificate records or links discovered on the official service. Request failures, invalid input, and parse failures increase `failureCount` in the `OUTPUT` key-value summary; they are never written as dataset records. A run with no saved certificate and at least one failure is `FAILED / FAILED`. If one or more certificates were saved before a later failure, it is `SUCCEEDED / PARTIAL`. A clean run is `SUCCEEDED / COMPLETED`, including a valid search with no matches. The default rights gate finishes as `SUCCEEDED / SKIPPED_POLICY` without making a request or writing a placeholder row.

The saved local dataset has three historical certificate records, each with 17 top-level fields and nested energy, property, metric, recommendation, and detail structures. The `details` array retains source key/value pairs, including repeated labels; the records remain unchanged and are not current source evidence.

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

## `postcode` (type: `string`):

UK postcode used with the official EPC search.

## `certificateUrls` (type: `array`):

Optional official energy-certificate URLs; these bypass postcode discovery.

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

Optional official EPC search URL.

## `maxItems` (type: `integer`):

Maximum real certificate records emitted, including link-only records when detail fetching is off.

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

Fetch each public certificate page and parse ratings, property details, and recommendations.

## `timeoutSecs` (type: `integer`):

Timeout for each government page request.

## `userAgent` (type: `string`):

Optional transparent HTTP user-agent string.

## `dataRightsConfirmed` (type: `boolean`):

Required before any source request. Confirm only if applicable reuse rights cover the requested certificate information and you have an appropriate lawful basis for any personal data, such as a property address.

## Actor input object example

```json
{
  "maxItems": 10,
  "includeDetails": false,
  "timeoutSecs": 30,
  "dataRightsConfirmed": 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/epc-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/epc-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/epc-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/epc-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/FzF4s5sygJdKI4MZt/builds/sOopTjmOM2mm57jMd/openapi.json