# Spain BORME Feed: New Companies, Dissolutions, Insolvency (`moment-data/spain-borme-company-acts-feed`) Actor

Daily feed of Spanish company acts from the official BORME (Registro Mercantil): new companies, dissolutions, extinctions, mergers, capital, name and address changes, insolvency (concurso). Province, event, legal form and keyword filters. Companies only, no person names. No API key.

- **URL**: https://apify.com/moment-data/spain-borme-company-acts-feed.md
- **Developed by:** [Luke Miller](https://apify.com/moment-data) (community)
- **Features:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $3.00 / 1,000 company acts

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

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

## Spain BORME Feed: New Companies, Dissolutions, Insolvency

Daily feed of **Spanish company acts** from the official **BORME** (Boletín Oficial del Registro Mercantil, Section A "Actos inscritos") published by the Agencia Estatal BOE. New companies (constituciones), dissolutions, extinctions, mergers and spin-offs, capital increases and reductions, registered office moves, name changes, insolvency (situación concursal), registry sheet closures and more. Every act becomes one clean JSON record with capital, CNAE code, municipality, postal code and business purpose. No API key, no login, no browser.

Run it daily in **"New since last run"** mode and you get only acts you have not seen before. That makes it a ready-made trigger for your CRM, credit-risk or KYC workflow.

### Who it's for

- **B2B sales and lead generation.** Reach new S.L. and S.A. companies in their first weeks: gestorías and accountants, banks, insurers, software vendors, office fit-out, telecoms, recruiters. Filter by province, keyword in the business purpose (`software`, `restaurante`, `solar`...) or minimum share capital.
- **Credit risk, debt collection and trade credit insurance.** Get alerts when a customer or supplier enters insolvency (concurso), is dissolved or extinguished, has its registry sheet closed, or reduces capital.
- **KYC / AML and vendor monitoring.** Track name changes, changes of legal form, registered office moves, mergers and sole-shareholder changes.
- **Market research and journalism.** Measure company formation and closures by province, sector (CNAE) and legal form.

### What you get

- `eventType` (the most important event in the act) and `eventTypes` (all events in it): `constitution`, `dissolution`, `extinction`, `merger`, `demerger`, `transformation`, `capitalIncrease`, `capitalReduction`, `addressChange`, `nameChange`, `purposeChange`, `insolvency`, `registryClosure`, `reopening`, `uncollectibleCredit`, `soleShareholderChange`, `officerChange`, `bylawsChange`, `website`, `bondIssue`, `branch`, `correction`, `other`.
- Company: `companyName`, `legalForm` (SL, SLU, SLP, SLL, SA, SAU, COOP, AIE, FOREIGN_BRANCH...), `province`, `provinceCode`, registry `registrySheet`, `inscriptionNumber`, `inscriptionDate`.
- New companies: `capitalEur`, `startDate`, `purpose` (objeto social), `cnae`, `municipality`, `postalCode`, `soleShareholderCompany` (only when the sole shareholder is itself a company).
- Changes: `newName`, `newLegalForm`, `newMunicipality`, `newPostalCode`, `capitalIncreaseEur`, `capitalReductionEur`, `resultingCapitalEur`, `dissolutionReason`, `mergerAbsorbedCompanies`, `website`, `bondIssueEur`.
- Insolvency: `insolvency[]` with `procedureNumber`, `final`, `resolutionDate`, `stage` (e.g. "Auto de declaración de concurso"), `phase` (declared, liquidation, agreement, concluded), `kind` (voluntary/necessary), `court`, `noAssets`.
- Officer changes: only counts (`appointments`, `cessations`, `revocations`, `reelections`) and role labels (e.g. "Adm. Unico", "Liquidador"), plus `liquidatorAppointed`.
- Links: `htmlUrl` and `pdfUrl` of the official BORME page, `bormeId`, `bormeNumber`, `publicationDate`, `entryNumber`.

**Privacy by design:** entity-level data only. The feed never outputs the names of administrators, directors, attorneys, liquidators, shareholders who are people, judges or insolvency administrators; it drops street addresses (municipality and postal code only) and the free text of "Otros conceptos" and corrections. Sole traders (Empresario Individual) are always excluded, and sociedades civiles (usually named after their partners) are excluded by default.

### Quick start

Click **Start** with the default input `{}`. You get about 30 new companies from the latest BORME edition in a few seconds.

Recipes:

- **Daily new companies in Madrid and Barcelona:** `{"mode":"sinceLastRun","provinces":["Madrid","Barcelona"],"daysBack":3,"maxItems":500,"stateKey":"mad-bcn"}`
- **Distress alerts, all Spain:** `{"eventTypes":["insolvency","dissolution","extinction","registryClosure","capitalReduction"],"maxItems":1000}`
- **New tech companies with at least EUR 10,000 capital:** `{"keywords":["software","tecnolog","inteligencia artificial"],"minCapital":10000,"daysBack":5,"maxItems":200}`
- **Mergers and changes of legal form:** `{"eventTypes":["merger","demerger","transformation"],"daysBack":5}`
- **Every act in one province:** `{"eventTypes":[],"provinces":["46"],"maxItems":2000}`

Schedule it every weekday morning (BORME appears around 07:30 Madrid time) in sinceLastRun mode with `daysBack` 3 and connect it to a webhook, Google Sheets, Make or Zapier.

### Input

| Field | Default | Notes |
|---|---|---|
| `eventTypes` | `["constitution"]` | list above; empty list = every act |
| `provinces` | all | names (Madrid, Málaga, Bizkaia, Alicante/Alacant) or INE codes (28, 29, 48, 03) |
| `legalForms` | all | SL, SLU, SLP, SLL, SLNE, SA, SAU, SAL, COOP, AIE, SC, SICAV, FOREIGN, FOREIGN_BRANCH, OTHER |
| `keywords` | none | matched against company name and business purpose, accent-insensitive |
| `minCapital` | none | EUR, constitution capital or resulting capital |
| `excludeSocietiesCiviles` | true | |
| `date` / `daysBack` | latest / 1 | number of BORME editions, newest first (Mon-Fri) |
| `mode` / `stateKey` | `window` / `default` | `sinceLastRun` dedupes across runs (60-day memory) |
| `maxItems` | 30 | up to 20,000 (also caps spend) |
| `concurrency` | 2 | 1-3 province pages in parallel |

### Output example

```json
{
  "publicationDate": "2026-10-30",
  "bormeId": "BORME-A-2026-210-06",
  "province": "BADAJOZ",
  "provinceCode": "06",
  "entryNumber": 486452,
  "companyName": "REVOLUX SOLAR S.L.",
  "legalForm": "SL",
  "eventType": "constitution",
  "eventTypes": ["constitution", "soleShareholderChange", "officerChange"],
  "capitalEur": 6000,
  "startDate": "2026-10-14",
  "purpose": "el reciclaje de material eléctrico, especialmente de paneles sola-res. Código C.N.A.E. de la actividad principal: 3832",
  "cnae": "3832",
  "municipality": "FUENTE DEL MAESTRE",
  "postalCode": "06360",
  "soleShareholderCompany": "MAESTRE INNOVATION S.L",
  "officerChanges": { "appointments": 2, "cessations": 0, "revocations": 0, "reelections": 0, "cancellations": 0, "roles": ["Adm. Solid."] },
  "registrySheet": "BA 36822",
  "inscriptionDate": "2026-10-23",
  "htmlUrl": "https://www.boe.es/diario_borme/txt.php?id=BORME-A-2026-210-06"
}
```

Insolvency example (excerpt):

```json
{
  "companyName": "CREACIONES LAYANES SL",
  "eventType": "insolvency",
  "insolvency": [{ "procedureNumber": "1006/2026", "final": true, "resolutionDate": "2026-07-28", "stage": "Auto de conclusión del concurso", "phase": "concluded", "court": "SECCION DE LO MERCANTIL DEL TRIBUNAL DE INSTANCIA DE ALACANT/ALICANTE. PLAZA Nº 3 CON SEDE EN ELX/ELCHE", "noAssets": true }]
}
```

A run summary (editions read, counts per event type, requests) is saved as the `OUTPUT` record in the key-value store. Fields that do not apply to an act are `null`.

### Pricing

Pay per event, no subscription:

| Event | Price |
|---|---|
| Actor start | $0.005 per run |
| `company-act-record` | $0.003 per company act delivered |

The default run (30 acts) costs about $0.095. A daily all-Spain distress watch (~350 acts) costs about $1.06 per day. Set `maxItems` or a maximum charge per run to cap your spend; the Actor stops delivering when the limit is reached.

### FAQ

**Where does the data come from?** From the Agencia Estatal Boletín Oficial del Estado: the BORME daily summary of the official open data API (`boe.es/datosabiertos/api/borme/sumario/YYYYMMDD`) and the official text version of each province's Section A page. The Actor sends a few small requests per run with an identifying User-Agent and respects boe.es robots.txt.

**Can I reuse it commercially?** BOE documents may be reused for commercial and non-commercial purposes under the BOE reuse conditions (aviso legal, Resolution of 27 June 2024): cite the source (Agencia Estatal BOE), do not alter the meaning, and do not suggest BOE endorses your use. This feed is not an official version; the legally valid text is the BORME publication linked in `htmlUrl`/`pdfUrl`. You are responsible for your own use, including data protection rules when you combine it with other data.

**Why are there no director or shareholder names?** By design. Many tools republish people's names from BORME; this feed is for company-level signals only, which keeps it simpler to use under GDPR.

**How fresh is it?** BORME is published Monday to Friday (not on national holidays), usually by 07:30 Madrid time. Acts are typically registered 3-10 days before publication (`inscriptionDate`).

**How many acts are there?** A weekday edition has roughly 2,000-3,000 company acts, including ~550 new companies, ~130 dissolutions, ~140 extinctions and dozens of insolvency entries.

**Does it cover Section C (announcements)?** Not yet. Section C (meeting calls, merger and capital-reduction announcements) is free text; tell us if you need it.

**Is the legal form always right?** It is derived from the company name suffix (SL, S.L.U., SOCIEDAD ANONIMA, AIE...). Unusual names fall into `OTHER`.

# Actor input Schema

## `eventTypes` (type: `array`):

Keep company acts that contain at least one of these events. Default: constitution (new companies). Clear the list to get every act. officerChange = board/administrator appointments and removals (only counts and role labels are returned, never names).

## `provinces` (type: `array`):

Registro Mercantil provinces, by name (Madrid, Barcelona, Valencia, Málaga, Alicante, Bizkaia...) or 2-digit INE code (28, 08, 46, 29, 03, 48). Accent-insensitive. Empty = all of Spain.

## `legalForms` (type: `array`):

Empty = all. Derived from the company name.

## `keywords` (type: `array`):

Keep acts whose company name or business purpose (objeto social) contains any of these words, accent-insensitive, e.g. solar, software, restaurante, inmobiliaria, transporte. Empty = all.

## `minCapital` (type: `integer`):

Optional. Keep acts that state a share capital (constitution capital or resulting capital after a change) of at least this amount.

## `excludeSocietiesCiviles` (type: `boolean`):

Civil partnerships are usually named after their partners; excluded by default. Sole traders (Empresario Individual) are always excluded.

## `date` (type: `string`):

YYYY-MM-DD. The newest BORME on or before this date is read. Default: today (Madrid time), so the latest edition.

## `daysBack` (type: `integer`):

Number of BORME editions to read, newest first. BORME is published Monday to Friday; one edition has ~2,000-3,000 company acts.

## `mode` (type: `string`):

sinceLastRun remembers delivered acts (per state key, 60 days) and only returns new ones. Use it for daily schedules with Publication days = 3.

## `stateKey` (type: `string`):

Separate memory for different sinceLastRun schedules.

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

Cap on delivered acts (also caps your spend).

## `concurrency` (type: `integer`):

Province pages fetched in parallel (polite to boe.es).

## Actor input object example

```json
{
  "eventTypes": [
    "constitution"
  ],
  "excludeSocietiesCiviles": true,
  "daysBack": 1,
  "mode": "window",
  "stateKey": "default",
  "maxItems": 30,
  "concurrency": 2
}
```

# Actor output Schema

## `acts` (type: `string`):

One record per company act published in BORME Section A.

## `summary` (type: `string`):

Editions read, filters, counts per event type.

# 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 = {};

// Run the Actor and wait for it to finish
const run = await client.actor("moment-data/spain-borme-company-acts-feed").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 = {}

# Run the Actor and wait for it to finish
run = client.actor("moment-data/spain-borme-company-acts-feed").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 '{}' |
apify call moment-data/spain-borme-company-acts-feed --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,moment-data/spain-borme-company-acts-feed"
        }
    }
}
```

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/EEinWCfsV3jav2kqq/builds/BiyokGXZzqhE8e38f/openapi.json
