How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

OpenMercantil Legal API

Spanish mercantile-law layer (derecho mercantil): legislation corpus + article texts + act→norm bridge. Distributes the consolidated BOE legal corpus structured by OpenMercantil so LLMs and agents can cite it as a source. License: consolidated text from the BOE, reused under Ley 37/2007 (re-use of public sector information); the official version is always boe.es. Informational only — NOT legal advice. Court judgments are NOT exposed here (CENDOJ is kept as a citation-index only, per CGPJ…

OpenMercantil Legal API is one of 18 APIs that OpenMercantil publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Legal. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 7 operations across 7 paths, and defines 19 schemas. It is described by OpenAPI 3.1.0, at version 1.9.3.

Requests are made against a single base URL, https://openmercantil.es.

7 operations 7 paths 19 schemas 6 GET1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.0
API Version
1.9.3
Base URL
https://openmercantil.es
Authentication
API Key, HTTP Bearer, API Key
Terms of Service
Resource Areas
1

Authentication & Security 3

OpenMercantil Legal API declares 3 security schemes for authenticating requests. An API key is passed in the header as X-API-Key (apiKey). It accepts HTTP bearer tokens (opaque omk_* credential) (bearerAuth). An API key is passed in the cookie as ob_sess (cookieAuth).

  • apiKey — Optional opaque omk API credential for public GETs. Anonymous access remains valid; a credential with the operation's x-api-credential-scope (or public:read) s…
  • bearerAuth — Optional Authorization: Bearer transport for the same opaque omk API credential accepted by X-API-Key. It is not a JWT or OAuth access token.
  • cookieAuth — Browser session cookie set after login at /mi-cuenta/login. Mutations also require X-CSRF-Token header (obtain via GET /api/v1/user/me).

Paths & Operations 7

Across 7 paths, the API surfaces 7 operations — 6 GET, 1 POST. Each is listed below with its method, path, parameters, and response codes.

Legal 7

Spanish mercantile-law layer (derecho mercantil): legislation corpus + article texts + act→norm bridge. Distributes the consolidated BOE legal corpus structured by OpenMercantil s…

POST
/api/v1/empresa/{slug}/informe-legal
Create the authenticated user's redacted corporate legal report
createCompanyLegalReport 2 params body → 200400401402403404413429
GET
/api/v1/legal/norms
Index of core Spanish mercantile-law norms
getLegalNorms → 200429503
GET
/api/v1/legal/normdeprecated
Index mercantile-law norms through the singular legacy alias
getLegacyLegalNorms → 200429503
GET
/api/v1/legal/norm/{slug}
Detail of a single mercantile-law norm (with act↔norm bridge)
getLegalNormBySlug 1 param → 200404429503
GET
/api/v1/legal/article/{norm}/{n}
Consolidated text of a single article
getLegalArticleByNormByN 2 params → 200404429503
GET
/api/v1/legal/act-map
BORME act type → governing norm bridge (full or single)
getLegalActMap → 200429503
GET
/api/v1/legal/act-map/{acto}
Governing norm for a single BORME act type
getLegalActMapByActo 1 param → 200404429503

Schemas 19

The contract defines 19 schemas that model the data the API accepts and returns. The most detailed are ErrorResponse (35 properties), LegalReportAxis (15 properties), LegalNormFull (14 properties), LegalNormSummary (8 properties). Each schema is shown below with its type and property counts.

ErrorResponse
object
Closed compatibility envelope for public/account errors. Route-specific schemas narrow these fields further where required.
35 properties 1 required
JsonValue
A JSON value used only inside explicitly documented extension maps.
LegalActMapEntry
LegalActMapResponse
LegalArticleResponse
LegalCitableFact
objectnull
Single atomic, verbatim-citable fact for AI answers (GEO envelope).
5 properties
LegalKeyArticle
object
6 properties
LegalLicenseFields
object
License/attribution/disclaimer envelope present in every legal-layer response. The legal corpus is consolidated BOE text re-used under Ley 37/2007 (NOT CC BY 4…
5 properties
LegalNormFull
object
14 properties
LegalNormResponse
LegalNormSummary
object
8 properties
LegalNormsIndexResponse
LegalRegulatedAct
object
BORME act type governed by this norm (law→data bridge).
5 properties
LegalReportAxis
object
One documentary axis in the redacted corporate legal-history projection. Presence records sourced events; it does not assert wrongdoing, solvency, current stat…
15 properties 4 required
LegalReportDocument
object
3 properties 3 required
LegalReportPaymentRequiredError
LegalReportRequest
object
The body carries only the CSRF fallback. Entitlement, pricing, beta status and the daily idempotency key are server-owned.
1 property
LegalReportResponse
object
7 properties 7 required
RequestBodyTooLargeError
object
2 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

openmercantil-legal-api-openapi.yml Raw ↑

Other APIs OpenMercantil publishes across the network.

OpenMercantil API Credentials API
OpenMercantil Billing API
OpenMercantil BORME API
OpenMercantil Companies API
OpenMercantil Datasets API
OpenMercantil Graph API
OpenMercantil Integrations API
OpenMercantil Persons API
OpenMercantil Public Procurement API
OpenMercantil Risk Signals API
OpenMercantil Search API
OpenMercantil Sectors API
Where this information came from

This is an independent, third-party profile of OpenMercantil Legal API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.