Spain Property & Judicial Auctions Scraper | BOE

Spain Property & Judicial Auctions Scraper at a glance

Spain Property & Judicial Auctions Scraper is a ready-to-run Apify actor from abotapi for collecting web data. Its output documents 32 fields, including auction id, estado, tiposubasta, cuentaexpediente and fechainicio, which you can export as JSON, CSV or Excel or read through the Apify API. It costs $2.00 per 1,000 results on the Apify Free plan and from $1.20 on paid plans, with smaller per-run or optional feature charges listed on Apify.

Runs on: Apify cloud: console, API, schedules and integrations
Data type: Web data
Region: Europe
Pricing: $2.00 per 1,000 results (Free plan), from $1.20 on paid plans
Output: 32 documented fields · JSON, CSV, Excel
Inputs: 27 options

What Spain Property & Judicial Auctions Scraper can do

Every auction status. Search across all five portal statuses (upcoming, judicial enforcement, subsequent, cancelled, finished) or read specific auction links you paste in.
Money fields and lots. Each record carries claim amount, appraised value, valuation, minimum bid, deposit, bid tranches, lot count, and the full lot details with documents.
Dates and authority. Conclusion, start, and publication dates plus the enforcing authority, province, locality, street address, and postal code - everything needed to filter and route a deal.
Bid status without an account. Each enriched record says whether the auction received bids and where its bidding period stands. Bid amounts are the one thing the portal answers only to registered users, so the actor reports the public status instead of inventing a number.
Documents linked. Bases, inventory, and appraisal attachments are collected as URLs on every record.
Monitoring ready. Incremental mode with resume and change fields flags what moved between runs, so you can schedule recurring checks cheaply.

Choose what to collect

These inputs let you configure Spain Property & Judicial Auctions Scraper | BOE. Open the actor on Apify to enter your values and review the current options.

Supported input fields
Input	What it controls
`mode`string · required	Search walks auction listings by status and date windows. URL mode reads the specific auctions you paste. Choices: search, url
`estados`array	Search mode: auction statuses to walk. EJ = judicial enforcement (open auctions with dates), PU = upcoming public, SU = subsequent, CA = cancelled, FS = finished. CA and FS return very large sets; combine them with a narrow date window.
`fechaFinDesde`string	Search mode: only auctions concluding on or after this date (ISO date, e.g. 2026-10-01). Leave empty for no lower bound.
`fechaFinHasta`string	Search mode: only auctions concluding on or before this date (ISO date, e.g. 2026-10-08). Leave empty for no upper bound.
`fechaInicioDesde`string	Search mode: only auctions starting on or after this date (ISO date). Leave empty for no lower bound.
`fechaInicioHasta`string	Search mode: only auctions starting on or before this date (ISO date). Leave empty for no upper bound.
`tipoBien`string	Search mode: real estate auctions only (Inmuebles, the default and the original behaviour), vehicles only (Vehiculos), or all asset types. URL mode is unaffected. Choices: I, V,

Show 20 more inputs

More input fields
Input	What it controls
`sortField`string	Search mode: the portal's own sort. Conclusion date (default and the original behaviour), auction identifier, status, or minimum bid. Choices: SUBASTA.FECHA_FIN, SUBASTA.ID_SUBASTA_ORDENAR, SUBASTA.ESTADO.CODIGO, SUBASTA.POSTURA_MINIMA_MINIMA_LOTES
`sortOrder`string	Search mode: ascending (default and the original behaviour) or descending. Choices: asc, desc
`valorMinimo`string	Search and URL modes: keep only auctions whose auction value is at least this many euros. Evaluated after each auction is read; needs detail reads on to apply everywhere.
`valorMaximo`string	Search and URL modes: keep only auctions whose auction value is at most this many euros. Evaluated after each auction is read; needs detail reads on to apply everywhere.
`provincia`string	Search mode: narrow to one province - type its NAME (e.g. Madrid, Barcelona, Alicante; accents optional) or its INE code (01-52, e.g. 28 = Madrid). Leave empty for all provinces.
`idSubasta`string	Search mode: fetch one auction by its identifier (e.g. SUB-JA-2025-251191). The status filter is skipped for this lookup (the identifier already picks one auction); the date windows still apply.
`startUrls`array	URL mode: auction detail links, each carrying its auction id (detalleSubasta.php?idSub=SUB-...). Both id styles work - judicial (SUB-JA-...) and administrative/tax (SUB-AT-... with its alphanumeric tail). A link carrying extra search-context parameters (idBus, idLote) is read the same way, and a bare auction id (SUB-JA-...) is accepted too. The auction id is read from the link; entries are read in order.
`urls`array	Alias for Auction links, accepted under the name other Apify actors use for URL mode. Each entry is an auction detail link; entries are read in order.
`fetchDetails`boolean	Read each auction's detail page (valuation, minimum bid, deposit, authority contact, property lots, documents). Turn off for a faster listing-only run. Each enriched auction is billed once as detail enrichment.
`maxItems`integer	Stop after this many records. This is THE cap: the run stops when it is reached or when listings run out.
`maxPages`integer	Advanced. Rarely needed: cap the listing pages read per status. Zero means no page cap; Max items still stops the run.
`resumeFromRunId`string	Paste a previous run ID or dataset ID to continue a large pull without returning items already collected there.
`incrementalMode`boolean	Turn this on for daily or recurring monitoring. The first run returns every matching auction as NEW. Later runs compare the full auction snapshot (amounts, dates, status, lots, authority) against the stored baseline and return only NEW and UPDATED auctions. Volatile fields that move without the auction changing - document list, authority phone/fax/email - are excluded from the comparison by default, and Ignore fields (below) adds more. Turn on Emit unchanged or Emit expired only when you also want those rows returned (and billed). State is kept separately for each status, date-window and link setup; use State key to name or deliberately share a monitoring campaign.
`stateKey`string	Optional. Name this monitoring campaign to keep its state stable, or deliberately share state across differently configured runs. Leave empty to let the actor derive a key automatically from the statuses and date settings.
`emitUnchanged`boolean	Off by default. Turn on to also return auctions that have not changed since the last run, marked UNCHANGED. This returns, and bills, extra rows you already have.
`emitExpired`boolean	Off by default. Turn on to also return auctions that were present in a previous run but are no longer found, marked EXPIRED. Only produced once a run has fully scanned the tracked search.
`ignoreFieldsForChanges`array	Incremental mode: changes to only these fields do not mark a record UPDATED. Defaults cover rotating document tokens and volatile counters.
`mcpConnectors`array	Optionally send results into the apps you already use, via Model Context Protocol (MCP) connectors. Authorize one under Apify, Settings, API & Integrations, then select it here. Notion gets a rich page-per-item export; other connectors get a best-effort write or digest. Leave empty to skip; never changes the dataset output.
`notionParentPageUrl`string	URL or id of the Notion page under which item pages are created. Required to enable the Notion export; ignored by other connectors.
`maxNotifyListings`integer	Cap on items written to each connector per run. Does not affect the dataset.

Fields in the output

The documented dataset includes the fields below. Availability can depend on the source page and selected mode.

idSubAuction id

estadoestado

tipoSubastatipoSubasta

cuentaExpedientecuentaExpediente

fechaIniciofechaInicio

fechaConclusionConclusion

fechaPublicacionfechaPublicacion

cantidadReclamadacantidadReclamada

valorSubastaAuction value

tasaciontasacion

pujaMinimaMinimum bid

tramostramos

Show 20 more fields

depositodeposito

loteslotes

pujasEstadopujasEstado

hasBidshasBids

autoridadCodigoautoridadCodigo

autoridadDescripcionautoridadDescripcion

provinciaprovincia

localidadlocalidad

direcciondireccion

codigoPostalcodigoPostal

detailUrlDetail link (link)

changeTypechangeType

changedFieldschangedFields

firstSeenAtfirstSeenAt

lastSeenAtlastSeenAt

bienesbienes

descripcionLot

situacionPosesoriasituacionPosesoria

visitablevisitable

inscripcionRegistralinscripcionRegistral

Example output

An example from this actor’s documentation. Values are illustrative; this is not a fresh live result.

{
  "idSub": "SUB-JA-2025-251191",
  "estado": "EJ",
  "tipoSubasta": "JUDICIAL EN VÍA DE APREMIO",
  "cuentaExpediente": "3527 0000 05 1106 24",
  "fechaInicio": "18-09-2026 18:00:00 CET (ISO: 2026-09-18T18:00:00+02:00)",
  "fechaConclusion": "08-10-2026 18:00:24 CET (ISO: 2026-10-08T18:00:24+02:00)",
  "fechaPublicacion": "26-09-2026",
  "cantidadReclamada": "278.898,39 €",
  "valorSubasta": "230.518,81 €",
  "tasacion": "0,00 €",
  "pujaMinima": "Sin puja mínima",
  "deposito": "11.525,94 €",
  "pujasEstado": "concluido periodo de pujas",
  "hasBids": true,
  "provincia": "MADRID",
  "localidad": "MADRID",
  "detailUrl": "https://subastas.boe.es/detalleSubasta.php?idSub=SUB-JA-2025-251191",
  "changeType": "NEW"
}

Ways to use this data

Who: Real estate investors tracking foreclosure and enforcement auctions nationwide.
Who: Legal and compliance researchers monitoring auction activity by court or authority.
Who: Data teams enriching property pipelines with BOE auction records and valuation history.

Before you run

Start with a small input and check the resulting records against your expected fields. Source content and actor options can change; the current Apify listing is the reference for availability and pricing.

Questions about this actor

What data does Spain Property & Judicial Auctions Scraper return?

Spain Property & Judicial Auctions Scraper returns 32 documented fields, including auction id, estado, tiposubasta, cuentaexpediente, fechainicio, conclusion, fechapublicacion and cantidadreclamada. Availability of each field depends on the source page and the selected mode.

How much does Spain Property & Judicial Auctions Scraper cost?

It costs $2.00 per 1,000 results on the Apify Free plan and from $1.20 on paid plans, with smaller per-run or optional feature charges listed on Apify. The Apify listing shows the current rate for every plan.

What data comes back from each auction?

Every record carries the auction id, status, type, file number, conclusion/start/publication dates, claim amount, appraised value, valuation, minimum bid, deposit, bid tranches, lot count, bid status, enforcing authority, province, locality, address, postal code, and the detail link. With detail enrichment on you also get every lot with its description, address, possession status, and linked documents.

Why did my run return no results?

Check the status filter and date window first - narrow windows combined with a single status usually mean genuinely no auctions conclude in that range. Upcoming (PU) and subsequent (SU) auctions are announced before their dates are set, so their date fields are legitimately empty. Link mode only accepts auction-detail URLs carrying an auction id. Runs that cannot reach the portal fail loudly instead of returning an empty success.

Can I schedule recurring runs to monitor new auctions?

Yes. Turn on incremental mode with a state key, and each run only emits new or changed auctions with changeType, changedFields, and first/last-seen timestamps. Schedule it in Apify and pair it with the Notion connector to receive only what moved.