🔔 Spain BORME Company Acts Scraper

One record per registered company act ('Actos inscritos') — company name, act text, province, BORME document id and publication date — extracted as structured data from the official JSON summary and section XML (not image PDFs).

One structured registry_record per record from the boe.es open-data BORME daily summary (JSON) → per-province section XML chain, logged-out. Public, logged-out, robots-honoured.

Output is one borme_company_act row per result; billing is pay-per-event, the value event being one registry record (a $0.02 start fee per run, then $0.02 per registry record). Source: www.boe.es.

No login, no API key and no CAPTCHA solving are involved: the source is read logged-out with an identified contact User-Agent.

Who buys this

Buyers usually search for BORME or Spain company registry.

• Sales and lead-generation teams building lists from BORME.
• KYB, onboarding and compliance teams checking Spain company registry.
• Market researchers and data teams that need the official record as rows.

📊 Sample Output

Real rows from run u1dGjWpj3uH48I7PG on build 0.1.10 (2026-09-23), the same input as the Quick start below — every value is as the source published it (emails masked, long text shortened):

acto_number	company_name	province	document_id	publication_date	release_date
358199	GUARDIANES DE LA GALAXIA SL	ALICANTE/ALACANT	BORME-A-2026-146-03	2026-07-31	2026-07-31
358200	WONDER PLACE GROUP SL	ALICANTE/ALACANT	BORME-A-2026-146-03	2026-07-31	2026-07-31
358201	PRODUCTOS DEL MAR ANCAVICO SL	ALICANTE/ALACANT	BORME-A-2026-146-03	2026-07-31	2026-07-31
358202	FALEN SUMINISTROS Y SERVICIOS SL	ALICANTE/ALACANT	BORME-A-2026-146-03	2026-07-31	2026-07-31
358203	MEDITERRANEAN OCEAN PROPERTIES SL	ALICANTE/ALACANT	BORME-A-2026-146-03	2026-07-31	2026-07-31
358204	RUSTIC & CHIC MEDITERRANEAN SL	ALICANTE/ALACANT	BORME-A-2026-146-03	2026-07-31	2026-07-31
358205	AROMADRIVE SL	ALICANTE/ALACANT	BORME-A-2026-146-03	2026-07-31	2026-07-31
358206	SISTEMAS WRITER 400 SL	ALICANTE/ALACANT	BORME-A-2026-146-03	2026-07-31	2026-07-31

The run finished with the status message: CAPPED: delivered 50 of 51 unique rows (maxRecords=50). billable=50

✅ What you get

Each row is flat JSON with these fields (from the dataset schema and the sample run; a field the source does not publish for a given row is null):

• record_type (string) — e.g. borme_company_act
• acto_number (string/null) — e.g. 358199
• company_name (string/null) — e.g. GUARDIANES DE LA GALAXIA SL
• act_text (string/null) — e.g. GUARDIANES DE LA GALAXIA SL. Cambio de domicilio social. AVDA MARINERS DE LA VIL
• province (string/null) — e.g. ALICANTE/ALACANT
• document_id (string/null) — e.g. BORME-A-2026-146-03
• publication_date (string/null) — e.g. 2026-07-31
• source (string/null) — e.g. spain-borme-company-acts
• release_date (string/null) — e.g. 2026-07-31
• source_url (string/null) — e.g. https://www.boe.es/datosabiertos/api/borme/sumario/20260731
• observed_at (string/null) — e.g. 2026-09-23T16:19:42Z
• terminal (string/integer/null) — null in every sample row
• reported_total (string/integer/null) — null in every sample row
• raw_seen (string/integer/null) — null in every sample row
• duplicates (string/integer/null) — null in every sample row
• unique_found (string/integer/null) — null in every sample row
• delivered (string/integer/null) — null in every sample row
• scope (string/integer/null) — null in every sample row
• note (string/integer/null) — null in every sample row

✅ What you get

• record_type (string) — e.g. borme_company_act
• acto_number (string/null) — e.g. 358199
• company_name (string/null) — e.g. GUARDIANES DE LA GALAXIA SL
• act_text (string/null) — e.g. GUARDIANES DE LA GALAXIA SL. Cambio de domicilio social. AVDA MARINERS DE LA VIL
• province (string/null) — e.g. ALICANTE/ALACANT
• document_id (string/null) — e.g. BORME-A-2026-146-03
• publication_date (string/null) — e.g. 2026-07-31
• source (string/null) — e.g. spain-borme-company-acts
• release_date (string/null) — e.g. 2026-07-31
• source_url (string/null) — e.g. https://www.boe.es/datosabiertos/api/borme/sumario/20260731
• observed_at (string/null) — e.g. 2026-09-18T05:53:59Z
• terminal (string/integer/null) — null in every sample row
• reported_total (string/integer/null) — null in every sample row
• raw_seen (string/integer/null) — null in every sample row
• duplicates (string/integer/null) — null in every sample row
• unique_found (string/integer/null) — null in every sample row
• delivered (string/integer/null) — null in every sample row
• scope (string/integer/null) — null in every sample row
• note (string/integer/null) — null in every sample row

What you get

One registry_record per entity, deduplicated on the source-native id. Fields the source does not publish are honest null. A run_receipt row carries the source URL, scope, and delivered/duplicate counts.

⚙️ Sample inputs

1. Quick start — the Store example (this is what the sample above came from)

{
  "date": "20260731",
  "maxRecords": 10
}

The sample run charged exactly: 1 × $0.02 apify-actor-start + 50 × $0.02 registry_record = $1.02 on the Free tier — every delivered row was billed.

2. A smaller, narrowed run

{
  "date": "20260731",
  "maxRecords": 5
}

Caps the run at 5 rows — about $0.12 on the Free tier ($0.02 start + 5 × $0.02). date narrows what the source is asked for.

3. A full-size run

{
  "date": "20260731",
  "maxRecords": 2000
}

Up to 2000 rows (the schema default for maxRecords) — about $40.02 on the Free tier ($0.02 start + 2000 × $0.02) if the source has that many.

4. A filtered run

{
  "date": "20260731",
  "maxRecords": 10,
  "fieldMatch": {
    "company_name": "GUARDIANES DE LA GALAXIA SL"
  }
}

Keeps only rows whose company_name contains GUARDIANES DE LA GALAXIA SL (a value from the sample run above), matched case-insensitively after the source is read and before the maxRecords cap, so the cap counts matches and only delivered matches are billed. searchText does the same across every column. Zero matches end the run as EMPTY_SELECTION with no row charged — if the source has moved on since that sample run, pick a value you see in your own first run. The source is still read in full — this narrows what you receive and pay for, not what the source serves.

🧾 JSON sample record

One real record from run u1dGjWpj3uH48I7PG, exactly as it lands in the dataset (emails masked, long text shortened):

{
  "record_type": "borme_company_act",
  "acto_number": "358199",
  "company_name": "GUARDIANES DE LA GALAXIA SL",
  "act_text": "GUARDIANES DE LA GALAXIA SL. Cambio de domicilio social. AVDA MARINERS DE LA VILA JOIOSA 1 Bl.2 18 - PUERTA (VILLAJOYOSA). Cambio de objeto social. Actividad Principal: Organización, gestión, contratación y comercialización de eventos, fest",
  "province": "ALICANTE/ALACANT",
  "document_id": "BORME-A-2026-146-03",
  "publication_date": "2026-07-31",
  "source": "spain-borme-company-acts",
  "release_date": "2026-07-31",
  "source_url": "https://www.boe.es/datosabiertos/api/borme/sumario/20260731",
  "observed_at": "2026-09-23T16:19:42Z"
}

🔧 How it works

Source. The actor reads www.boe.es — endpoints: https://www.boe.es, https://www.boe.es/datosabiertos/api/borme/sumario/. Public pages and feeds only; nothing behind a login.

Transport. Plain HTTPS from the Apify platform, no proxy. robots.txt is read first and a disallowed path is never fetched. Every request carries an identified contact User-Agent.

Charging. Each registry record is charged at the moment it is pushed (registry_record); a row that fails to charge is not delivered, so the dataset count always equals the charged count.

🔧 How it works

How it behaves

Scope is a publication day (the date input; blank = most recent bulletin). The JSON summary is fetched with Accept: application/json; each section XML is parsed for company-act entries. maxRecords caps the count. Duplicates, outages, and schema drift charge nothing.

What is not done. No login, no cookie or CAPTCHA bypass, no private or personal-account data, no browser automation.

💰 Pricing example

Event	Free	Bronze	Silver	Gold
Actor Start (apify-actor-start)	$0.02	$0.02	$0.02	$0.02
Registry Record (registry_record)	$0.02	$0.018	$0.016	$0.0134

Worked at the live Free-tier price:

• 8 registry records: $0.02 start + 8 × $0.02 = $0.18
• 25 registry records: $0.02 start + 25 × $0.02 = $0.52
• 2000 registry records: $0.02 start + 2000 × $0.02 = $40.02

A run that delivers zero rows charges the $0.02 start fee only. A BLOCKED run (source refused) fails loud and charges no value event. The start fee is charged once per GB of run memory; the default run memory is 4096 MB.

Yield on the sample run: CAPPED: delivered 50 of 51 unique rows (maxRecords=50). billable=50. maxRecords is a hard ceiling on what is delivered and billed, never a target.

⚖️ Legal & ToS

This actor reads public, logged-out pages and feeds published by www.boe.es. It collects only what the source publishes to any visitor, keeps to the source's robots rules (checked on every run), identifies itself with a contact User-Agent, and does not access accounts, private data or anything behind authentication. Use the output in line with the source's terms and your local law; the intended use is B2B research and monitoring.

❓ FAQ

Q: Do I need an API key or a login?
A: No. The source (www.boe.es) is read logged-out; the input schema has no key field and the actor carries no secrets.

Q: Why did my run return 0 rows?
A: Read the run's status message. GENUINE_EMPTY means the source was read and had nothing in scope for your input; BLOCKED means the source refused and the run failed without billing a value event — retry later or narrow the input. A zero-row run bills the start fee only.

Q: How many rows can one run return?
A: Up to maxRecords (default 2000). Raise the cap for a bigger run; you pay per delivered row.

Q: How fresh is the data?
A: Every run reads the source live at run time; nothing is cached between runs. Put it on a schedule for a continuous feed.

Q: What formats can I export?
A: The dataset downloads as JSON, CSV, Excel, XML or RSS from the run's Dataset tab or the Apify API, and any run can push to a webhook or integration.

Q: How is this different from the other NexGen Watch actors actors?
A: Same output shape and billing model; this one covers www.boe.es. The siblings under Related Actors cover the other sources or slices — run several on one schedule for a combined feed.

Q: Are there rate limits?
A: The actor paces itself against the source and honours its robots rules; there is no per-buyer limit beyond your Apify plan's concurrency.

🆘 Troubleshooting

• Run FAILED with BLOCKED → the source refused the request or changed its page shape → nothing was billed beyond the start fee; retry after a while, and if it persists open an Issue with the run id.
• Status says CAPPED → your cap (maxRecords) was reached → raise it for a bigger run.
• Input validation error on start → a field is outside the schema's allowed values → start from the Quick start block and change one field at a time.
• Run TIMED-OUT → a very wide request on a slow day → raise the run timeout in Run options or narrow the input; what was delivered before the timeout is still in the dataset.

🔗 Related Actors

• Slovakia Public-Sector Partners Register — One record per registered public-sector partner from the official RPVS OData — official ID, business name, validity dates, and beneficial owners when…
• Spain AEMPS Medicines Registry (CIMA) — One record per authorized medicine from the official CIMA REST API — national code, name, laboratory, authorization status; presentation/route/docume…
• Spain BOE Official Records — One structured official_notice per entry in the Boletín Oficial del Estado daily summary, from the official BOE open-data API — keyless, logged-out
• Spain CNMC Numbering Assignments — One record per telephone-numbering allocation from the official CNMC bd-num.zip, with record_type preserving WHICH numbering table it came from and t…
• Texas Active Franchise Taxpayers — One record per active TX franchise taxpayer (identity, SOS/COA file number, organization type, charter/status dates, right-to-transact status) from t…
• UK Licensed Sponsor Register (Workers) — Each record carries the organisation, town/city, county, licence type & rating, and immigration route from the newest official CSV, with the register…
• 🏢 About NexGen Watch — NexGen Watch is a catalog of more than 300 public data actors built on official sources, pay-per-result. Browse the catalog at apify.com/nexgenwatch.

⭐ Found this useful?

If this actor saved you a manual check, a quick review on the Apify Store helps other teams find it. Feature request or a source that changed? Open it from the Issues tab — every one is read.