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 Sectors API

CNAE sector aggregates, ratios and company listings

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

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

This API exposes 8 operations across 8 paths, and defines 10 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

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

8 operations 8 paths 10 schemas 8 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Server
https://openmercantil.es
Authentication
API Key, API Key, HTTP Bearer, API Key
Terms of Service
Resource Areas
1

Authentication & Security 4

OpenMercantil Sectors API declares 4 security schemes for authenticating requests. An API key is passed in the cookie as ob_sess (cookieAuth). 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 session (sessionCookie).

  • 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).
  • 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.
  • sessionCookie — Session cookie issued after web sign-in, required only for billing endpoints.

Paths & Operations 8

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

Sectors 8

CNAE sector aggregates, ratios and company listings

GET
/api/v1/sector/{cnae}/companies
Get companies by CNAE sector code
getSectorByCnaeCompanies 5 params → 200400422429503
GET
/api/v1/sector/{cnae}/ratios
Get sector aggregated ratios
getSectorByCnaeRatios 2 params → 200304404429503
GET
/api/v1/cnae/tree
Hierarchical CNAE tree
getCnaeTree → 200429503
GET
/api/v1/cnae/{code}
CNAE code metadata
getCnaeByCode 1 param → 200404429503
GET
/api/v1/sector/{code}/companies
List Companies In A Sector
getSectorCompanies 2 params → 200404429
GET
/api/v1/sector/{code}/ratios
Get Sector Financial Ratios
getSectorRatios 1 param → 200404429
GET
/api/v1/sectores/stats
Get Sector Aggregate Statistics
getSectorStats → 200429
GET
/api/v1/sectores/stats.csv
Export Sector Aggregate Statistics As CSV
getSectorStatsCsv → 200429

Schemas 10

The contract defines 10 schemas that model the data the API accepts and returns. The most detailed are ErrorResponse (35 properties), CompanySearchItem (12 properties), CnaeNode (7 properties), SectorCompaniesResponse (7 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.
SectorRatio
object
5 properties 5 required
CnaeTreeResponse
object
1 property 1 required
CnaeNode
object
CNAE node. Catalog loaders may add official explanatory fields.
7 properties
SectorCompaniesResponse
object
7 properties 7 required
SectorRatiosResponse
object
2 properties 2 required
CompanySearchItem
object
12 properties 4 required
ProjectionUnavailableError
object
Fail-closed projection outage. Clients must not reinterpret this response as an empty or negative result.
3 properties 3 required
ErrorResponse_2
object
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

openmercantil-sectors-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 Legal API
OpenMercantil Persons API
OpenMercantil Public Procurement API
OpenMercantil Search API
OpenMercantil Sources API
Where this information came from

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