# Spain New Companies & BORME Registry Events (`trilling_karst/borme-spain-companies`) Actor

Every new Spanish company (constitución) and Registro Mercantil event from the official BORME, as clean JSON: business purpose, address, municipality, capital, start date, registry data. Official open data, no proxies.

- **URL**: https://apify.com/trilling\_karst/borme-spain-companies.md
- **Developed by:** [Álvaro](https://apify.com/trilling_karst) (community)
- **Categories:** Lead generation, Business
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$2.00 / 1,000 results

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

### What does Spain New Companies & BORME Registry Events do?

It turns the **BORME** (Boletín Oficial del Registro Mercantil, Spain's official commercial-registry gazette) into clean, structured JSON/CSV/Excel. You get **every new Spanish company (constitución) published each weekday**, about 400–500 a day, with its business purpose (objeto social), registered address, municipality, share capital, start date and registry data. It also covers every other registry event: appointments, resignations, address changes, capital increases, dissolutions, insolvencies (concurso), mergers and more.

The data comes straight from the **official BOE open-data API**. There are no proxies, no scraping of third-party sites and no login.

### Why use it?

- **Sales and lead generation:** reach brand-new companies while they're still choosing an accountant, bank, insurer, web agency, software or office. Filter by province and keywords ("restaurante", "software", "inmobiliaria").
- **Market research:** count incorporations by sector, province or capital size, and spot trends early.
- **KYC and monitoring:** follow registry events such as dissolution, insolvency, address changes and officer changes for the companies you care about.
- **AI agents and RAG:** a stable, documented feed of Spanish corporate events in clean JSON.

### How to use it

1. Leave the defaults to get **new companies from the last 3 days**. Or set a start and end date (up to one year per run).
2. Optionally filter by **provinces** (e.g. `MADRID`, `BARCELONA`, `VALENCIA`) and **keywords** in the company name or business purpose.
3. Choose which **event types** to keep. The default is new companies only; pick *All events* to get every registry entry.
4. Run it and download the results as JSON, CSV, Excel, or through the API.
5. **Tip:** schedule it daily with *Last N days = 1* to get a fresh list of new companies every weekday morning.

### Output example

```json
{
  "publicationDate": "2026-09-23",
  "province": "ARABA/ÁLAVA",
  "companyName": "ONDARE RESIDENCIA ULETA, S.L",
  "legalForm": "SL",
  "municipality": "VITORIA-GASTEIZ",
  "address": "C/ ESTADIO DE MENDIZORROTZA, PASEO DE CERVANTES S/ (VITORIA-GASTEIZ)",
  "capitalEur": 3000.0,
  "startOfOperations": "2026-07-29",
  "purpose": "Servicios de hospedaje a estudiantes universitarios...",
  "eventTypes": ["incorporation", "sole_shareholder_declared", "appointments"],
  "registry": {"section": "8", "sheet": "VI 23242", "inscription": "1", "inscriptionDate": "2026-09-16"},
  "entryNumber": 425090,
  "bormeId": "BORME-A-2026-184-01",
  "sourcePdf": "https://www.boe.es/borme/dias/2026/09/23/pdfs/BORME-A-2026-184-01.pdf"
}
```

Each item also contains an `events` array with every act in the entry (type, Spanish label, text and parsed fields, such as the amount for capital changes).

### Event types

`incorporation` (constitución) · `appointments` (nombramientos) · `resignations` (ceses/dimisiones) · `revocations` · `reelections` · `address_change` · `purpose_change` · `purpose_extension` · `name_change` · `capital_increase` · `capital_reduction` · `sole_shareholder_declared` · `sole_shareholder_lost` · `dissolution` · `extinction` · `insolvency` (situación concursal) · `merger_absorption` · `merger_union` · `partial_spinoff` · `total_spinoff` · `transformation` · `bylaw_changes` · `other`

### How much does it cost?

Pay per result: you pay only for the companies/entries you get. One weekday of every new company in Spain is about 450 results. A daily feed for a single province is usually 5–150 results.

### Data quality

The parser is tested against thousands of real entries. Registry data is parsed in 99.9% of entries, capital in 99.5% of incorporations and business purpose in 100%. The text is exactly what BORME publishes, including its occasional OCR typos, and the original PDF link is included for verification.

### Personal data (GDPR)

BORME publishes directors' and attorneys' names. **By default this Actor hides them.** Turn on *Include people* only if you have a lawful basis to process them. You are responsible for complying with the GDPR/LOPDGDD, for example no unsolicited marketing to individuals.

### FAQ

**How fresh is the data?** BORME is published Monday–Friday at about 07:30 CET, and the Actor reads it the same morning.
**Does it include the NIF/CIF?** No. BORME doesn't publish tax IDs.
**Historical data?** Yes. Any date range since 2009, up to one year per run.
**Something missing or wrong?** Open an issue on the Actor page. Fixes usually ship within days.

# Actor input Schema

## `lastDays` (type: `integer`):

Used when Start date is empty: the last N calendar days up to End date (BORME is not published on weekends). For a daily schedule use 1.

## `startDate` (type: `string`):

YYYY-MM-DD. Overrides Last N days.

## `endDate` (type: `string`):

YYYY-MM-DD. Defaults to today.

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

Keep entries that contain at least one of these events. Default: new companies only. Pick 'All events' for every registry entry.

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

Optional. Province names as printed in BORME, e.g. MADRID, BARCELONA, VALENCIA, BIZKAIA, ARABA. Empty = all of Spain.

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

Optional. Keep only entries whose company name or business purpose contains any keyword (case-insensitive), e.g. restaurante, software, inmobiliaria.

## `includePeople` (type: `boolean`):

Adds the officers published in BORME. These are personal data: you are responsible for using them lawfully under the GDPR (e.g. no unsolicited marketing to individuals without a legal basis).

## `includeRawText` (type: `boolean`):

Adds the full original text of each entry.

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

Stop after this many results (0 = no limit).

## Actor input object example

```json
{
  "lastDays": 3,
  "eventTypes": [
    "incorporation"
  ],
  "includePeople": false,
  "includeRawText": false,
  "maxItems": 0
}
```

# Actor output Schema

## `results` (type: `string`):

All dataset items as JSON: company name, legal form, province, municipality, address, capital, business purpose, start date, registry data, events and source links.

## `overview` (type: `string`):

The main fields only, as shown in the Overview table.

# 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("trilling_karst/borme-spain-companies").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("trilling_karst/borme-spain-companies").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 trilling_karst/borme-spain-companies --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,trilling_karst/borme-spain-companies"
        }
    }
}
```

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/NbiHyqa94RArgwsRI/builds/5CRmZyEmFzinBYvqJ/openapi.json