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

Public read-only connector catalog. Never exposes credentials, OAuth tokens, webhook secrets or operator actions.

Documentation Provider Profile APIs.io OpenAPI GitHub

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

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

This API exposes 3 operations across 3 paths, and defines 13 schemas. It is described by OpenAPI 3.2.0, at version 1.9.3.

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

3 operations 3 paths 13 schemas 2 GET1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.9.3
Server
https://openmercantil.es
Authentication
API Key, API Key, HTTP Bearer
Contact
OpenMercantil
License
Source-specific upstream terms; see response catalog metadata
Terms of Service
View terms
Resource Areas
1

Authentication & Security 3

OpenMercantil Integrations API declares 3 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).

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

Paths & Operations 3

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

Integrations 3

Public read-only connector catalog. Never exposes credentials, OAuth tokens, webhook secrets or operator actions.

POST
/api/v1/stripe-webhook
Receive a signed Stripe event
receiveStripeWebhook 1 param body → 200400413500503
GET
/api/v1/integrations
List public integration capabilities
listIntegrations 2 params → 200304400429503
GET
/api/v1/integrations/{slug}
Get one public integration contract
getIntegration 2 params → 200304400404429503

Schemas 13

The contract defines 13 schemas that model the data the API accepts and returns. The most detailed are ErrorResponse (35 properties), PublicIntegration (18 properties), PublicSourcePolicyMetadata (12 properties), IntegrationListResponse (8 properties). Each schema is shown below with its type and property counts.

RequestBodyTooLargeError
object
2 properties 2 required
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.
SourceCatalogEnvelope
object
4 properties 3 required
PublicIntegrationEgressPolicy
object
Legal permission from the active source catalog. It does not claim that a technical projection is deployed.
4 properties 4 required
PublicSourcePolicyMetadata
object
12 properties 8 required
PublicIntegrationCoverage
object
3 properties
PublicIntegrationTransport
object
Technical read-plane status. unavailable has no endpoint; separateauthority delegates fail-closed validation to the listed endpoint contract and is not a healt…
4 properties 4 required
IntegrationListResponse
object
8 properties 7 required
StripeWebhookEventRequest
object
Stripe Event envelope. The exact signed raw bytes, not a reserialized object, are used for verification. Provider extension fields remain typed JSON and are no…
7 properties 3 required
PublicIntegration
object
18 properties 15 required
PublicIntegrationContract
object
5 properties 3 required
IntegrationDetailResponse
object
7 properties 6 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

openmercantil-integrations-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 Legal API
AE Profile APIs.io
OpenMercantil Persons API
AE Profile APIs.io
OpenMercantil Public Procurement API
AE Profile APIs.io
OpenMercantil Search API
AE Profile APIs.io
OpenMercantil Sectors API
AE Profile APIs.io
OpenMercantil Sources API
AE Profile APIs.io
#Integration
← Back to O APIs
API Details
ID
openmercantil:openmercantil-integrations-api
Server
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-integrations-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/openmercantil-integrations-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 Integrations 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.