Search registry events
search_eventsSearch BORME registry events (since 2009) across companies by publication date, province, act type and company name, newest first or oldest first.
Use it for questions about many companies. For one known company use company_history; to find a company use search_companies; for one day's totals use daily_digest.
Returns JSON {count, events: [{event_id, date, borme_id, province, company_name, company_slug, acts: [{act_type, act_type_raw, roles, payload}], registral}], next_cursor, has_more}, plus company_name_match, plan_window and hidden_by_plan when they apply. While has_more is true, pass next_cursor as cursor for the next page; with order=asc, save the last next_cursor to poll for later events.
Read-only; one request per call against your daily quota. Without an API key (X-API-Key header, https://bormeapi.com/account) only the last 7 days are searched. If the page is empty and hidden_by_plan or company_name_match has a note, relay it. Invalid input is rejected with a reason.
Tool call template
This tool declares no required parameters. Add optional parameters from the input schema as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {},
"name": "search_events"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| cnae | No | Optional CNAE code or prefix of 2 to 4 digits, with or without a dot, e.g. "47", "4711" or "47.11". Needs the Pro or Risk plan; a new account's free 7-day Risk trial includes it. Matches the printed digits, in any classification or, with cnae_version, only in that one. For the company's sector on the CNAE-2009 axis use division. Cannot be combined with cursor or order "asc". | |
| limit | No | Maximum events returned, integer 1-200, e.g. 20 (default 50). | |
| order | No | Optional, "desc" (default, newest first) or "asc" (oldest first, from date_from), e.g. "asc". For an oldest-first feed, save next_cursor from the last response, even when has_more is false, and reuse it when polling later. The cursor follows the publication date: an event added later with a publication date that the cursor has already passed is not returned. | |
| cursor | No | Optional: the unchanged next_cursor value from the previous response, to fetch the next page, e.g. "djF8ZHwyMDI2LTA4LTI2fHNoYTE6MDA2N2U3YzdhZDQ2ZmQ1NGNiMTEzOGQzMTg4NWIxZDg3OGZlMjg5Ng". It keeps its sort order. Keep the same filters to continue the same result set; with other filters the query still starts after the saved position. | |
| date_to | No | Latest publication date, inclusive, YYYY-MM-DD, e.g. 2026-09-30. Optional; defaults to the latest day held. | |
| division | No | Optional two-digit CNAE-2009 division, e.g. "62": acts whose company had that sector on the act's BORME publication date. Each event then carries sector_division, sector_provenance and sector_source_event_id; provenance own (a code printed in this act), carried (a code printed in an earlier act of the company, also under an earlier name), model (a language-model decision, only with include_inferred=true) or carry_ended_ambiguous (a later printed code without a division ended the carried sector; no sector). The answer names division_axis "CNAE-2009" and policy_version. A sector can change when a later decision, or an act published on or before that date but added to our data later, classifies the company. Same attribution as act_stats sectors. Needs the Pro or Risk plan. Cannot be combined with cnae, cnae_version, cnae_version_basis, cursor or order "asc". | |
| act_types | No | Optional list of act type enums; an event matches if it has any of them, e.g. ["INCORPORATION"] or ["INSOLVENCY_DECLARATION", "INSOLVENCY_STATUS"]. Full list: list_act_types. Barcelona prints some acts as free text under "Otros conceptos": recognised wording is mapped to a normalised act type, while act_type_raw remains "Otros conceptos". The payload retains the source text, including any sole shareholder's name. When a revocation and a new appointment appear in the same entry, the API maps the combination to RE_ELECTIONS; this is an API classification and does not establish that the source describes a re-election. Reprocessed events keep their event_id, but their acts can change. | |
| date_from | No | Earliest publication date, inclusive, YYYY-MM-DD, e.g. 2026-09-01. Optional; data starts on 2009-01-02. Without a key it is moved up to 7 days ago (plan_window says so). | |
| provinces | No | Optional list of BORME province names, accent- and case-insensitive, e.g. ["MADRID", "CADIZ", "VIZCAYA"]. An autonomous community stands for all of its provinces, e.g. ["Basque Country"] or ["Cataluña"]. Full list: the resource borme://provinces. | |
| holder_kind | No | Optional, one of investment_vehicle or investment_manager, e.g. investment_vehicle. Returns events that originate a sole-shareholder or legal-person director link classified, from the entity's name alone, as investment_vehicle (a possible investment vehicle: SCR, ECR, FCR, FCRE, SICAV, capital riesgo, private equity, fondo de inversión) or investment_manager (a possible investment manager: SGEIC, SGIIC). It does not return every subsequent act mentioning that entity. A director link may originate in a re-election act. The name alone does not establish registration with the CNMV. This filter does not identify entities whose names contain none of these indicators. date_from and date_to may be at most 366 days apart; both dates are included, so at most 367 calendar days. Without date_from, the range covers 90 calendar days ending on date_to or today, including that day. Pro plan. | |
| cnae_version | No | Optional classification version, one of "1993", "2009" or "2025". Requires cnae. If omitted, printed codes match whatever their cnae_version, including null. If supplied, only codes with that cnae_version match: named in the act (basis stated) or assigned by our rules (date, code). "2009" therefore also matches codes whose classification is not named in acts published before 1 January 2025, provided CNAE-2009 contains the code (our dating rule by BORME publication date; RD 10/2025 entered into force on 16 January 2025); add cnae_version_basis ["stated"] for the codes whose classification the act names. | |
| include_inferred | No | Optional, with division only, default false, e.g. true. With division, true also matches and shows sectors that depend on a language-model decision (sector_provenance model, acts published from 2024-11-05), and the response includes model, prompt and min_confidence. Without include_inferred=true, acts whose sector depends on a language-model decision do not match division. true is refused while those sectors are not offered, and always with cnae; without division or cnae any value is refused. | |
| cnae_version_basis | No | Optional, with cnae only: a list of one or more of "stated" (the act names the classification), "date" (before 1 January 2025, CNAE-2009 by our dating rule), "code" (from 1 January 2025, only one classification contains the code), "equivalent" (both contain it, equivalent per the INE correspondence table) and "ambiguous" (both contain it, not equivalent). Keeps printed codes whose cnae_version_basis is one of them; to keep the previous result of a cnae_version filter, keep it and add e.g. ["stated"]. | |
| company_name_contains | No | Optional part of the company name, case- and accent-insensitive, e.g. "mercadona"; use at least 3 letters or digits for a selective search. % and _ match literally. It filters events; to look a company up by name, call search_companies first. |