Spain BOE Official Records avatar

Spain BOE Official Records

Pricing

from $13.40 / 1,000 spain boe official records records

Go to Apify Store
Spain BOE Official Records

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.

Pricing

from $13.40 / 1,000 spain boe official records records

Rating

0.0

(0)

Developer

NexGen Watch

NexGen Watch

Maintained by Community

Actor stats

0

Bookmarked

3

Total users

2

Monthly active users

6 days ago

Last modified

Share

🔔 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.

Difference: One record per disposición / anuncio published in the daily summary of Spain's State Official Gazette (BOE) — identifier, section code + name, department, epigraph, title, publication date, and the canonical PDF / HTML / XML document links. Distinct from our BORME actor: BORME is the mercantile registry gazette (company incorporations, appointments, accounts); this is the STATE bulletin BOE — laws, royal decrees, orders, and official announcements. Different bulletin, different records.

Output is one boe_notice row per result; billing is pay-per-event, the value event being one spain boe official records record (a $0.02 start fee per run, then $0.02 per spain boe official records record).

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 BOE or Spain official gazette.

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

📊 Sample Output

Spain BOE Official Records sample output — a table of real spain boe official records record rows (identifier, control, section_name, department_name) from run 4cGlnjv3CfDLzhk7I on build 0.1.7

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

identifiercontrolsection_namedepartment_nameepigraphpublication_date
BOE-A-2026-166522026/12670I. Disposiciones generalesJEFATURA DEL ESTADOComunidad Autónoma de Galicia. Autopistas2026-07-31
BOE-A-2026-166532026/12668I. Disposiciones generalesJEFATURA DEL ESTADOSeguridad Social2026-07-31
BOE-A-2026-166542026/12669I. Disposiciones generalesJEFATURA DEL ESTADOSistema Nacional de Salud2026-07-31
BOE-A-2026-166552026/12469I. Disposiciones generalesMINISTERIO DE DEFENSAFuerzas Armadas. Jornada y horarios de trabajo2026-07-31
BOE-A-2026-166562026/12559I. Disposiciones generalesMINISTERIO DEL INTERIORSubvenciones2026-07-31
BOE-A-2026-166572026/12675I. Disposiciones generalesMINISTERIO DEL INTERIOREmergencia de interés nacional2026-07-31
BOE-A-2026-166582026/12470I. Disposiciones generalesMINISTERIO DE TRANSPORTES Y MOVILIDAD SOSTENIBLERutas aéreas2026-07-31
BOE-A-2026-166592026/12671I. Disposiciones generalesMINISTERIO DE EDUCACIÓN, FORMACIÓN PROFESIONAL Y DEPORTESAulas de Tecnología Aplicada. Aulas de Emprendimiento2026-07-31

The run finished with the status message: CAPPED: delivered 50 of 189 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. boe_notice
  • identifier (string/null) — e.g. BOE-A-2026-16652
  • control (string/null) — e.g. 2026/12670
  • section_code (string/null) — e.g. 1
  • section_name (string/null) — e.g. I. Disposiciones generales
  • department_name (string/null) — e.g. JEFATURA DEL ESTADO
  • epigraph (string/null) — e.g. Comunidad Autónoma de Galicia. Autopistas
  • title (string/null) — e.g. Ley Orgánica 3/2026, de 29 de julio, de transferencia de la titularidad y compet
  • publication_date (string/null) — e.g. 2026-07-31
  • document_pdf_url (string/null) — e.g. https://www.boe.es/boe/dias/2026/07/31/pdfs/BOE-A-2026-16652.pdf
  • document_html_url (string/null) — e.g. https://www.boe.es/diario_boe/txt.php?id=BOE-A-2026-16652
  • document_xml_url (string/null) — e.g. https://www.boe.es/diario_boe/xml.php?id=BOE-A-2026-16652
  • source (string/null) — e.g. spain-boe-official-records
  • release_date (string/null) — e.g. 2026-07-31
  • source_url (string/null) — e.g. https://www.boe.es/datosabiertos/api/boe/sumario/20260731
  • observed_at (string/null) — e.g. 2026-09-18T20:11:15Z
  • license (string/integer/null) — e.g. BOE open-data reuse conditions (Agencia Estatal BOE)
  • attribution (string/integer/null) — e.g. Source: Agencia Estatal Boletín Oficial del Estado (BOE) — www.boe.es, open-data
  • 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. boe_notice
  • identifier (string/null) — e.g. BOE-A-2026-16652
  • control (string/null) — e.g. 2026/12670
  • section_code (string/null) — e.g. 1
  • section_name (string/null) — e.g. I. Disposiciones generales
  • department_name (string/null) — e.g. JEFATURA DEL ESTADO
  • epigraph (string/null) — e.g. Comunidad Autónoma de Galicia. Autopistas
  • title (string/null) — e.g. Ley Orgánica 3/2026, de 29 de julio, de transferencia de la titularidad y compet
  • publication_date (string/null) — e.g. 2026-07-31
  • document_pdf_url (string/null) — e.g. https://www.boe.es/boe/dias/2026/07/31/pdfs/BOE-A-2026-16652.pdf
  • document_html_url (string/null) — e.g. https://www.boe.es/diario_boe/txt.php?id=BOE-A-2026-16652
  • document_xml_url (string/null) — e.g. https://www.boe.es/diario_boe/xml.php?id=BOE-A-2026-16652
  • source (string/null) — e.g. spain-boe-official-records
  • release_date (string/null) — e.g. 2026-07-31
  • source_url (string/null) — e.g. https://www.boe.es/datosabiertos/api/boe/sumario/20260731
  • observed_at (string/null) — e.g. 2026-09-18T19:49:51Z
  • license (string/integer/null) — e.g. BOE open-data reuse conditions (Agencia Estatal BOE)
  • attribution (string/integer/null) — e.g. Source: Agencia Estatal Boletín Oficial del Estado (BOE) — www.boe.es, open-data
  • 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 official_notice per summary entry, deduplicated on the BOE identifier. A run_receipt row carries the source URL, publication date, scope, reuse attribution, and delivered/duplicate totals.

⚙️ Sample inputs

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

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

The sample run charged exactly: 1 × $0.02 apify-actor-start + 50 × $0.02 official_notice = $1.02 on the Free tier — every delivered row was billed. If you leave maxRecords out, the run delivers at most 50 rows (the schema default); pass a number up to 2000000 for a bigger export. An explicit value is always honoured up to that maximum.

2. A smaller, narrowed run

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

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

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

Up to 5000 rows — about $100.02 on the Free tier ($0.02 start + 5000 × $0.02) if the source has that many; maxRecords goes up to 2000000.

4. A filtered run

{
"maxRecords": 10,
"date": "20260731",
"fieldMatch": {
"section_name": "I. Disposiciones generales"
}
}

Keeps only rows whose section_name contains I. Disposiciones generales (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 4cGlnjv3CfDLzhk7I, exactly as it lands in the dataset (emails masked, long text shortened):

{
"record_type": "boe_notice",
"identifier": "BOE-A-2026-16652",
"control": "2026/12670",
"section_code": "1",
"section_name": "I. Disposiciones generales",
"department_name": "JEFATURA DEL ESTADO",
"epigraph": "Comunidad Autónoma de Galicia. Autopistas",
"title": "Ley Orgánica 3/2026, de 29 de julio, de transferencia de la titularidad y competencias de la autopista del Atlántico (AP-9) a la Comunidad Autónoma de Galicia.",
"publication_date": "2026-07-31",
"document_pdf_url": "https://www.boe.es/boe/dias/2026/07/31/pdfs/BOE-A-2026-16652.pdf",
"document_html_url": "https://www.boe.es/diario_boe/txt.php?id=BOE-A-2026-16652",
"document_xml_url": "https://www.boe.es/diario_boe/xml.php?id=BOE-A-2026-16652",
"source": "spain-boe-official-records",
"release_date": "2026-07-31",
"source_url": "https://www.boe.es/datosabiertos/api/boe/sumario/20260731",
"observed_at": "2026-09-18T20:11:15Z",
"license": "BOE open-data reuse conditions (Agencia Estatal BOE)",
"attribution": "Source: Agencia Estatal Boletín Oficial del Estado (BOE) — www.boe.es, open-data reuse notice"
}

🔧 How it works

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. Pacing: CRAWL_DELAY=0.0.

Terminal states. A run ends NORMAL, CAPPED (your cap was reached), PARTIAL (something was withheld and the message says what), GENUINE_EMPTY (the source was read and truly had nothing in scope) or BLOCKED (the source refused or changed shape — the run FAILS loud and bills nothing). A zero-row run is never reported as a silent success.

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

🔧 How it works

How it behaves

Reads the official documented BOE open-data daily-summary API for the requested date (defaults to today), walking every section → department → item. Sundays and holidays return HTTP 404 — these are GENUINE-EMPTY days delivered as a SUCCEEDED empty run that charges nothing, never an error. The BOE open-data reuse notice is carried as attribution.

Source

https://www.boe.es/datosabiertos/api/boe/sumario/{YYYYMMDD}

Attribution

Source: Agencia Estatal Boletín Oficial del Estado (BOE) — www.boe.es. Carried under the BOE open-data reuse conditions.

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

💰 Pricing example

EventFreeBronzeSilverGold
Actor Start (apify-actor-start)$0.02$0.02$0.02$0.02
Spain BOE Official Records record (official_notice)$0.02$0.018$0.016$0.0134

Worked at the live Free-tier price:

  • 8 spain boe official records records: $0.02 start + 8 × $0.02 = $0.18
  • 25 spain boe official records records: $0.02 start + 25 × $0.02 = $0.52
  • 50 spain boe official records records: $0.02 start + 50 × $0.02 = $1.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 189 unique rows (maxRecords=50). billable=50. maxRecords is a hard ceiling on what is delivered and billed, never a target.

This actor reads public data only. 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 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 50). 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 Spain BOE Official Records. 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 (CRAWL_DELAY=0.0) 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.
  • Seattle Business License Tax Certificates — One record per active Seattle business-licence tax certificate (legal + trade name, ownership type, NAICS activity, licence start date, address, city…
  • 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 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 s…
  • 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…
  • 🏢 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.