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

Customer-support writes. Anonymous creation requires explicit privacy consent; replies require an authenticated owner session and CSRF. Ticket data is never exposed through the public MCP.

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

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

This API exposes 2 operations across 2 paths, and defines 10 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.

2 operations 2 paths 10 schemas 2 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
Terms of Service
Resource Areas
1

Authentication & Security 1

OpenMercantil Support API declares 1 security scheme for authenticating requests. An API key is passed in the cookie as ob_sess (cookieAuth).

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

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

Support 2

Customer-support writes. Anonymous creation requires explicit privacy consent; replies require an authenticated owner session and CSRF. Ticket data is never exposed through the pu…

POST
/api/v1/support/ticket
Create a customer-support ticket
createSupportTicket body → 201400413429503
POST
/api/v1/support/ticket/{id}/reply
Reply to a support ticket owned by the authenticated user
replySupportTicket 2 params body → 200400401403413429503

Schemas 10

The contract defines 10 schemas that model the data the API accepts and returns. The most detailed are ErrorResponse (35 properties), SupportTicketCreateRequest (8 properties), SupportErrorResponse (4 properties), SupportTicketCreatedResponse (3 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.
OkResponse
object
1 property 1 required
RequestBodyTooLargeError
object
2 properties 2 required
SupportErrorResponse
object
4 properties 2 required
SupportReplyRequest
object
1 property 1 required
SupportRequestErrorResponse
Support validation/ownership errors carry ok=false; shared body-reader and action-budget errors use the generic API error envelope.
SupportTicketCategory
string
Stable support-routing category accepted by the current account schema.
SupportTicketCreateRequest
object
Customer-supplied support content. Privacy consent is purpose-bound to handling and protecting this request; it is not marketing consent.
8 properties 5 required
SupportTicketCreatedResponse
object
3 properties 3 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

openmercantil-support-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 Risk Signals API
OpenMercantil Search API
Where this information came from

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