# Aepd Spain Data Protection Resolution Scraper (`jungle_synthesizer/aepd-spain-data-protection-resolution-scraper`) Actor

Extracts and structures Spain's AEPD data protection enforcement resolutions: fine amounts, infringed GDPR articles, severity, and final outcome parsed from the resolution text, with reposicion appeals linked back to their parent case.

- **URL**: https://apify.com/jungle\_synthesizer/aepd-spain-data-protection-resolution-scraper.md
- **Developed by:** [BowTiedRaccoon](https://apify.com/jungle_synthesizer) (community)
- **Categories:** Business, Lead generation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.80 / 1,000 record scrapeds

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

## AEPD Data Protection Resolution Scraper

Extract Spain's GDPR enforcement record from the [AEPD](https://www.aepd.es/informes-y-resoluciones/resoluciones), the country's data protection authority. Returns the fine amount, infringed articles, severity, and final outcome for every published resolution — sanctions, warnings, case closures, and reposición appeals — across the full ~47,000-document archive.

***

### AEPD Data Protection Resolution Scraper Features

- Extracts the fine actually paid, not just the headline figure — voluntary-payment settlements state both, and this returns the final one.
- Reads the infringed GDPR/LOPDGDD articles straight out of each resolution's operative finding.
- Classifies severity (leve / grave / muy grave) and the case outcome (sanctioned, archived, upheld, dismissed).
- Links every reposición appeal back to its parent case, so you see the case that was actually decided instead of a first-instance figure that got reduced or thrown out on appeal.
- Covers every AEPD procedure type in one pass — sanctions, rights-exercise procedures, warnings, cooperation cases, and archived investigations alike.
- Returns the respondent name parsed from the resolution text, plus the resolution and publication dates.

***

### Who Uses AEPD Enforcement Data?

- **Privacy counsel and DPOs** — benchmark fine amounts and enforcement trends against comparable cases before advising a client.
- **Compliance and GRC teams** — build an internal register of GDPR enforcement precedent by infringed article.
- **Legal researchers** — track how a specific RGPD/LOPDGDD article gets enforced over time, or at what severity tier.
- **Journalists and policy analysts** — follow Spain's enforcement volume, the EU's highest by resolution count.
- **Legaltech products** — feed a structured enforcement dataset into a search or alerting tool instead of a pile of PDFs.

***

### How AEPD Data Protection Resolution Scraper Works

1. Give it a record limit, or leave it unset for the full archive.
2. The scraper walks AEPD's published resolution listing from the newest case back.
3. Each resolution's text is read and reduced to structured fields — fine amount, articles, severity, outcome, respondent — alongside the listing's own file number and dates.
4. You get one row per resolution, appeals linked to their parent case, ready to filter or load straight into a spreadsheet or database.

***

### Input

```json
{
  "maxItems": 5
}
```

| Field      | Type    | Default | Description                                                                                   |
|------------|---------|---------|-----------------------------------------------------------------------------------------------|
| `maxItems` | integer | `0`     | Maximum number of resolutions to return. `0` = unlimited (the full ~47,000-document archive). |

***

### AEPD Data Protection Resolution Scraper Output Fields

```json
{
  "expediente": "EXP202416743",
  "procedure_reference": "PS-00035-2026",
  "resolution_type": "Procedimiento Sancionador",
  "is_reposicion": false,
  "parent_expediente": null,
  "resolution_date": "2026-09-16T00:00:00Z",
  "publication_date": "2026-09-23T11:25:00Z",
  "respondent": "HOY VOY A CONDUCIR, S.L.",
  "fine_amount_eur": 30000,
  "infringed_articles": ["art. 32 RGPD"],
  "infringement_severity": "grave",
  "outcome": "sancionado",
  "summary": "Con fecha 28 de mayo de 2026, la Presidencia de la Agencia Española de Protección de Datos acordó iniciar procedimiento sancionador...",
  "full_text": "1/23\nExpediente Nº: EXP202416743\nRESOLUCIÓN DE TERMINACIÓN DEL PROCEDIMIENTO...",
  "pdf_url": "https://www.aepd.es/documento/ps-00035-2026.pdf",
  "source_url": "https://www.aepd.es/informes-y-resoluciones/resoluciones",
  "scraped_at": "2026-10-01T16:36:19.250Z"
}
```

| Field                   | Type    | Description                                                                                         |
|-------------------------|---------|-----------------------------------------------------------------------------------------------------|
| `expediente`            | string  | AEPD file number (e.g. `EXP202416743`) — the case's primary key.                                    |
| `procedure_reference`   | string  | The procedure-type-prefixed reference (e.g. `PS-00035-2026`).                                       |
| `resolution_type`       | string  | AEPD procedure type — sanction, rights-exercise, warning, cooperation, reposición appeal, and more. |
| `is_reposicion`         | boolean | `true` when this document is an appeal of an earlier resolution.                                    |
| `parent_expediente`     | string  | For a reposición appeal, the file number of the case under appeal.                                  |
| `resolution_date`       | string  | ISO-8601 date the resolution was signed.                                                            |
| `publication_date`      | string  | ISO-8601 date the resolution was published.                                                         |
| `respondent`            | string  | The entity investigated or sanctioned, when named in the resolution text.                           |
| `fine_amount_eur`       | number  | The fine actually payable — the post-reduction figure when a settlement states both.                |
| `infringed_articles`    | array   | GDPR/LOPDGDD articles cited in the resolution's finding (e.g. `"art. 32 RGPD"`).                    |
| `infringement_severity` | string  | `leve`, `grave`, or `muy grave`, when the resolution states a tier.                                 |
| `outcome`               | string  | `sancionado`, `archivado`, `estimado`, or `desestimado`.                                            |
| `summary`               | string  | A short excerpt from the resolution's opening finding.                                              |
| `full_text`             | string  | The resolution's full text.                                                                         |
| `pdf_url`               | string  | Link to the source resolution document.                                                             |
| `source_url`            | string  | The listing page this record was read from.                                                         |
| `scraped_at`            | string  | When this record was collected.                                                                     |

Some fields are genuinely absent on a given resolution rather than unpopulated by mistake — a case closure has no fine amount, and some respondents are described without a formal company identifier.

***

### Resuming a large crawl

Every run emits a `resumeCursor` in its Output. If a large crawl stops before it finishes — because it hit `maxItems`, your spend cap (`maxTotalChargeUsd`), or was aborted — start a new run with **the same input** plus that `resumeCursor` to continue from where it left off. The crawl resumes from the queued work the previous run didn't reach.

- You are **not re-charged** for records the earlier run already delivered.
- Resume within your account's run-retention window — on the free tier, roughly your 10 most recent runs. Once the source run is pruned, its `resumeCursor` is no longer valid.
- `resumeCursor` is opaque — supply it unmodified.

***

### FAQ

#### How do I scrape AEPD enforcement resolutions?

Run AEPD Data Protection Resolution Scraper with a `maxItems` value, or leave it at `0` for the full archive. No AEPD account or API key is required — the resolution listing is public.

#### What data can I get from AEPD's resolutions?

Fine amounts, infringed GDPR/LOPDGDD articles, severity tier, case outcome, respondent name, and the full resolution text, for every AEPD procedure type — not just sanctions.

#### Does this include recurso de reposición appeals?

Yes. Appeals are returned as their own records, each linked back to the `expediente` of the case they're appealing, so you can see the final outcome rather than a first-instance figure that was later reduced or overturned.

#### How much does AEPD Data Protection Resolution Scraper cost to run?

Pricing follows Apify's standard pay-per-event model for this actor — check the Pricing tab for current rates. A small `maxItems` run is inexpensive to try before committing to the full archive.

#### Can I get just the sanctions, not warnings or archived cases?

Every record carries a `resolution_type` field, so filter the output by type after the run. The scraper always covers the full procedure-type range in one pass.

***

### Need More Features?

Need custom fields, filters, or a different target site? [File an issue](https://console.apify.com/actors/issues) or get in touch.

### Why Use AEPD Data Protection Resolution Scraper?

- **Reads the resolution, not just the index** — fine amount, articles, severity, and outcome come from the text itself, not a search-result snippet.
- **Appeal-aware** — reposición cases are linked to their parent case, so a figure that was later reduced or annulled on appeal doesn't read as the final word.
- **Full procedure-type coverage** — sanctions, warnings, rights-exercise cases, and archived investigations are all in scope, not a cherry-picked subset.

# Actor input Schema

## `sp_intended_usage` (type: `string`):

What will this data feed? E.g. lead lists, KYB checks, price tracking.

## `sp_improvement_suggestions` (type: `string`):

Provide any feedback or suggestions for improvements.

## `sp_contact` (type: `string`):

We'll personally help with your use case. No spam.

## `resumeCursor` (type: `string`):

Leave empty for a fresh crawl. To CONTINUE a previous run where it stopped — without paying again for records you already received — paste the `resumeCursor` value from that run's Output (the run's OUTPUT key). Resume promptly: the previous run's data expires with your account's retention window (free tier: your ~10 most recent runs).

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

Maximum number of resolutions to return. 0 = unlimited (full corpus, ~47k resolutions across all AEPD procedure types).

## Actor input object example

```json
{
  "sp_intended_usage": "Describe your intended use...",
  "sp_improvement_suggestions": "Share your suggestions here...",
  "sp_contact": "Share your email here...",
  "maxItems": 5
}
```

# Actor output Schema

## `results` (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 = {
    "sp_intended_usage": "Describe your intended use...",
    "sp_improvement_suggestions": "Share your suggestions here...",
    "sp_contact": "Share your email here...",
    "maxItems": 5
};

// Run the Actor and wait for it to finish
const run = await client.actor("jungle_synthesizer/aepd-spain-data-protection-resolution-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 = {
    "sp_intended_usage": "Describe your intended use...",
    "sp_improvement_suggestions": "Share your suggestions here...",
    "sp_contact": "Share your email here...",
    "maxItems": 5,
}

# Run the Actor and wait for it to finish
run = client.actor("jungle_synthesizer/aepd-spain-data-protection-resolution-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 '{
  "sp_intended_usage": "Describe your intended use...",
  "sp_improvement_suggestions": "Share your suggestions here...",
  "sp_contact": "Share your email here...",
  "maxItems": 5
}' |
apify call jungle_synthesizer/aepd-spain-data-protection-resolution-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,jungle_synthesizer/aepd-spain-data-protection-resolution-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/uJgVVmpwQ5xiehYui/builds/hChRRHKLSRWme9c7g/openapi.json