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

Session-bound Stripe checkout, invoices and portal contracts. External actions are bounded, idempotent and never exposed through the public MCP.

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

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

This API exposes 8 operations across 7 paths, and defines 9 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 7 paths 9 schemas 2 GET6 POST

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 Billing 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 7 paths, the API surfaces 8 operations — 2 GET, 6 POST. Each is listed below with its method, path, parameters, and response codes.

Billing 8

Session-bound Stripe checkout, invoices and portal contracts. External actions are bounded, idempotent and never exposed through the public MCP.

POST
/api/v1/donation
Create a one-time donation Checkout session
postDonationCheckout 1 param body → 200400413429503
POST
/api/v1/credits/checkout
Create an idempotent credit-pack Checkout session
postCreditsCheckout 2 params body → 200400401403413429503
POST
/api/v1/checkout
Create a subscription Checkout session
postSubscriptionCheckout 2 params body → 200400401413429503403
GET
/api/v1/billing/invoices
List the authenticated user's invoices and subscription
getBillingInvoices → 200401429
GET
/api/v1/billing/portal
Redirect to the authenticated user's Stripe portal
getBillingPortal → 302400401429503
POST
/api/v1/billing/portal
Create a Stripe portal session as JSON
postBillingPortal 1 param → 200400401403429503
POST
/api/v1/portaldeprecated
Create a Stripe Customer Portal session through the legacy alias
postLegacyBillingPortal 1 param body → 200400401403429503
POST
/api/v1/stripe-webhook
Receive a signed Stripe event
receiveStripeWebhook 1 param body → 200400413500503

Schemas 9

The contract defines 9 schemas that model the data the API accepts and returns. The most detailed are ErrorResponse (35 properties), BillingInvoice (16 properties), BillingSubscription (14 properties), StripeWebhookEventRequest (7 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
BillingInvoice
object
Authenticated user's invoice metadata; URLs point to Stripe-hosted documents.
16 properties
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
BillingSubscription
object
Authenticated user's current subscription metadata.
14 properties
JsonValue
A JSON value used only inside explicitly documented extension maps.
StripeSessionResponse
object
2 properties 2 required
BillingInvoicesResponse
object
3 properties 3 required
ErrorResponse_2
object
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

openmercantil-billing-api-openapi.yml Raw ↑

Other APIs OpenMercantil publishes across the network.

OpenMercantil API Credentials 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 Sectors API
OpenMercantil Sources API
Where this information came from

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