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

Kanmon Payments API

The Payments API from Kanmon — 3 operation(s) for payments.

Kanmon Payments API is one of 14 APIs that Kanmon publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Payments. The published artifact set on APIs.io includes an OpenAPI specification.

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

Requests are made against 4 base URLs: https://api.kanmon.com, https://api.kanmon.dev, http://localhost:3333, https://workflow.concar.dev.

3 operations 3 paths 14 schemas 3 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2.0.0
Base URL
https://api.kanmon.com
Authentication
API Key
Resource Areas
1

Authentication & Security 1

Kanmon Payments API declares 1 security scheme for authenticating requests. An API key is passed in the header as Authorization (Authorization).

Paths & Operations 3

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

Payments 3
GET
/api/platform/v2/payments/{id}
Fetch a payment
getPaymentById 1 param → 200400403404429500
GET
/api/platform/v2/issued-products/{id}/payment-scheduledeprecated
Fetch payment schedule for an issued product
getPaymentScheduleForAIssuedProduct 8 params → 200400403404429500
GET
/api/platform/v2/payment-intents
Fetch payment intents
getPaymentIntents 9 params → 200400403429500

Schemas 14

The contract defines 14 schemas that model the data the API accepts and returns. The most detailed are PaymentIntent (27 properties), PaymentOrder (16 properties), BadRequestException (3 properties), IssuedProductNotFoundException (3 properties). Each schema is shown below with its type and property counts.

PaymentScheduleItem
object
3 properties 2 required
PaymentOrderStatus
string
The status of the payment.
IssuedProductNotFoundException
object
3 properties 3 required
InternalServerErrorException
object
3 properties 3 required
PaymentOrder
object
16 properties 15 required
PaginationResult
object
3 properties 3 required
TooManyRequestsException
object
3 properties 3 required
GetPaymentScheduleResponse
object
2 properties 2 required
PaymentOrderNotFoundException
object
3 properties 3 required
PaymentIntent
object
27 properties 26 required
PaymentIntentTriggerType
string
ForbiddenException
object
3 properties 3 required
BadRequestException
object
3 properties 3 required
GetPaymentIntentsResponse
object
2 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

kanmon-payments-api-openapi.yml Raw ↑

Other APIs Kanmon publishes across the network.

Kanmon Bank Accounts API
Kanmon Businesses API
Kanmon Connect Tokens API
Kanmon Documents API
Kanmon Draw Requests API
Kanmon Embedded Sessions API
Kanmon Integrated MCA API
Kanmon Invoices API
Kanmon Issued Products API
Kanmon Offers API
Kanmon Prequalifications API
Kanmon Sandbox Utilities API
Where this information came from

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