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
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
OpenMercantil

OpenMercantil Persons API

Documentary mentions of natural persons in BORME (officer roles). Persons treated as documentary mentions only — no DNI, no contact data, no scoring.

Documentation Provider Profile APIs.io OpenAPI GitHub

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

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

This API exposes 5 operations across 5 paths, organized into 2 resource areas, and defines 13 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.

5 operations 5 paths 13 schemas 5 GET

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
Contact
OpenMercantil
License
Source-specific upstream terms; see response catalog metadata
Terms of Service
View terms
Resource Areas
2

Authentication & Security 2

OpenMercantil Persons API declares 2 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).

  • 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.

Paths & Operations 5

Across 5 paths, the API surfaces 5 operations — 5 GET. They span 2 resource areas: Companies, Persons. Each is listed below with its method, path, parameters, and response codes.

Companies 1
GET
/api/v1/company/{slug}/officers
Get current and historical company officers
getCompanyBySlugOfficers 1 param → 200404429503
Persons 4

Documentary mentions of natural persons in BORME (officer roles). Persons treated as documentary mentions only — no DNI, no contact data, no scoring.

GET
/api/v1/persona/{slug}
Get documentary mentions of a person
getPersonaBySlug 1 param → 200404429503
GET
/api/v1/person/{slug}deprecated
Get documentary person mentions through the legacy English alias
getLegacyPersonBySlug 1 param → 200404429503
GET
/api/v1/person/search
Search documentary mentions of persons
getPersonSearch 2 params → 200400422429503
GET
/api/v1/persona/{slug}/contractsdeprecated
Person-to-procurement derivation (unavailable)
getPersonaBySlugContracts 1 param → 429503

Schemas 13

The contract defines 13 schemas that model the data the API accepts and returns. The most detailed are ErrorResponse (35 properties), PersonDocumentaryReport (18 properties), PublicSourcePolicyMetadata (12 properties), PersonSearchResponse (12 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.
OfficerDocumentaryMention
object
Documentary officer mention. It never contains DNI, contact details or a personal address.
7 properties
OfficerList
array
OfflineProjectionError
object
4 properties 1 required
PersonDocumentaryPosition
object
11 properties 11 required
PersonDocumentaryReport
object
Exact personpublicv1 report. It groups unresolved BORME name mentions and never proves identity or current vigency.
18 properties 17 required
PersonPublicProjectionMetadata
object
6 properties 6 required
PersonSearchItem
object
Documentary person search result; no DNI, contact data or personal address.
9 properties 9 required
PersonSearchResponse
object
12 properties 11 required
ProjectionUnavailableError
object
Fail-closed projection outage. Clients must not reinterpret this response as an empty or negative result.
3 properties 3 required
PublicSourcePolicyMetadata
object
12 properties 8 required
SourceCatalogEnvelope
object
4 properties 3 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

openmercantil-persons-api-openapi.yml Raw ↑

Other APIs OpenMercantil publishes across the network.

OpenMercantil API Credentials API
AE Profile APIs.io
OpenMercantil Billing API
AE Profile APIs.io
OpenMercantil BORME API
AE Profile APIs.io
OpenMercantil Companies API
AE Profile APIs.io
OpenMercantil Datasets API
AE Profile APIs.io
OpenMercantil Graph API
AE Profile APIs.io
OpenMercantil Integrations API
AE Profile APIs.io
OpenMercantil Legal API
AE Profile APIs.io
OpenMercantil Public Procurement API
AE Profile APIs.io
OpenMercantil Risk Signals API
AE Profile APIs.io
OpenMercantil Search API
AE Profile APIs.io
OpenMercantil Sectors API
AE Profile APIs.io
#Persons
← Back to O APIs
API Details
ID
openmercantil:openmercantil-persons-api
Base URL
https://openmercantil.es
Docs
https://openmercantil.es/api/documentacion
Provider
OpenMercantil
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=openmercantil-persons-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/openmercantil-persons-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

This is an independent, third-party profile of OpenMercantil Persons 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.