/borme/acts

POST /api/borme/acts

Price: 5 credits

Get all registered company acts (Sección A — Actos Inscritos) from a single daily BORME publication of the Spanish Official Commercial Register Gazette. A publication groups the acts registered in one province on one day. Identify it either by its full identifier (e.g. 'BORME-A-2026-116-08') or by year, issue number and province. Each act includes the register entry number, the company name, the act types (incorporation, director appointments and removals, capital changes, dissolution, etc.), the business purpose, registered office, share capital, sole shareholder, appointments and the register reference (volume, folio, sheet, entry, date).

How to use it

List the registered company acts published in one daily BORME 'Actos Inscritos' bulletin (one province, one day). Pass either 'borme_id' (e.g. 'BORME-A-2026-116-08') or year + number + province_code. Returns one entry per registered act with the company name, act types, business purpose, registered office, capital, sole shareholder, appointments and register reference.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• borme_id string nullable — Full BORME act publication identifier (examples: "BORME-A-2026-116-08")
• year integer nullable — Publication year of the act package (examples: 2026; min: 2001)
• number integer nullable — Daily gazette issue number (examples: 116; min: 1)
• province_code string nullable — Province code or name of the commercial register (examples: "08", "BARCELONA", "MADRID")

Response

• @type string (default: "BormeAct")
• registro_number string required
• company string required
• act_types array (default: [])
• text string nullable
• start_date string nullable
• objeto_social string nullable
• domicilio string nullable
• capital string nullable
• sole_shareholder string nullable
• appointments array (default: [])
  • @type string (default: "BormeAppointment")
  • role string nullable
  • name string nullable
• registry object nullable
  • @type string (default: "BormeRegistryData")
  • volume string nullable
  • folio string nullable
  • section string nullable
  • sheet string nullable
  • entry string nullable
  • date string nullable

Errors

• 422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.
• 408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.
• 412 — No BORME act publication found for the given identifier Retrying will not help: either the entity does not exist, or the input points at a different one.
• 429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.
• 500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.
• 529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.
• X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.
• X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.
• X-Retry-After — Seconds to wait before retrying. Present only on 429.