BORME – Boletín Oficial del Registro Mercantil (official gazette of the commercial register)
Agencia Estatal Boletín Oficial del Estado (AEBOE). API access, keys, rate limits and terms, each with its official source. Last checked 17 Oct 2026.
| Official site | https://www.boe.es/diario_borme/ Source: https://www.boe.es/datosabiertos/api/api.php · checked 17 Oct 2026 |
| Free API | Yes. Open-data API for the daily BORME summary (sumario) by date, in XML or JSON. BORME publishes registered company acts; it is not a company-extract API. Extracts from the Registro Mercantil are a separate service (not covered here). Source: https://www.boe.es/datosabiertos/api/api.php · checked 17 Oct 2026 |
| API docs | https://www.boe.es/datosabiertos/documentos/APIsumarioBORME.pdf Source: https://www.boe.es/datosabiertos/api/api.php · checked 17 Oct 2026 |
| Key / account | No. A keyless request for a date returned HTTP 200 JSON on our check. Source: https://www.boe.es/datosabiertos/api/borme/sumario/20261016 · checked 17 Oct 2026 |
| Data available | Daily BORME summary: sections (e.g. Section A 'Empresarios. Actos inscritos') with items per province, each linking to PDF, HTML and XML versions of the published acts. Source: https://www.boe.es/datosabiertos/api/borme/sumario/20261016 · checked 17 Oct 2026 |
| Rate limits | Not documented Not stated in the BORME API document. Source: https://www.boe.es/datosabiertos/documentos/APIsumarioBORME.pdf · checked 17 Oct 2026 |
| Licence / terms | BOE re-use conditions (standard licence approved by AEBOE resolution of 27 Jun 2024); reuse implies accepting them, with source attribution. Source: https://www.boe.es/informacion/aviso_legal/index.php · checked 17 Oct 2026 |
Up
HTTP 200 · 568 ms
Checked 06 Nov 2026, 12:17 UTC · 59.7% answering over 67 check(s)
Endpoint: https://www.boe.es/datosabiertos/api/borme/sumario/20261106
- statusBORME: status changed from Unexpected response to Up (HTTP 200).
- statusBORME: status changed from Up to Unexpected response (HTTP 404: expected JSON, got application/xml).
- statusBORME: status changed from Unexpected response to Up (HTTP 200).
- statusBORME: status changed from Up to Unexpected response (HTTP 404: expected JSON, got application/xml).
- statusBORME: status changed from Unexpected response to Up (HTTP 200).
- statusBORME: status changed from Up to Unexpected response (HTTP 404: expected JSON, got application/xml).
- statusBORME: status changed from Unexpected response to Up (HTTP 200).
- statusBORME: status changed from Up to Unexpected response (HTTP 404: expected JSON, got application/xml).
- statusBORME: status changed from Down to Up (HTTP 200).
- statusBORME: status changed from Up to Down (HTTP 500: server error).
- statusBORME: status changed from Unexpected response to Up (HTTP 200).
- statusBORME: status changed from Up to Unexpected response (HTTP 404: expected JSON, got application/xml).
- statusBORME: status changed from Unexpected response to Up (HTTP 200).
- statusBORME: status changed from Up to Unexpected response (HTTP 404: expected JSON, got application/xml).
- statusBORME: status changed from Unexpected response to Up (HTTP 200).
- statusBORME: status changed from Up to Unexpected response (HTTP 404: expected JSON, got application/xml).
- statusBORME: status changed from Unexpected response to Up (HTTP 200).
- statusBORME: status changed from Up to Unexpected response (HTTP 404: expected JSON, got application/xml).
- statusBORME: status changed from Unexpected response to Up (HTTP 200).
- statusBORME: status changed from Up to Unexpected response (HTTP 404: expected JSON, got application/xml).
- statusBORME: status changed from Unexpected response to Up (HTTP 200).
- statusBORME: status changed from Up to Unexpected response (HTTP 404: expected JSON, got application/xml).
- statusBORME: status changed from Unexpected response to Up (HTTP 200).
- statusBORME: status changed from Up to Unexpected response (HTTP 404: expected JSON, got application/xml).