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

Fermyon payments API

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

Fermyon payments API is one of 15 APIs that Fermyon 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 2 schemas. It is described by OpenAPI 3.1.0, at version 1.0.

Requests are made against a single base URL, https://cloud.fermyon.com.

3 operations 3 paths 2 schemas 2 GET1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.0
API Version
1.0
Server
https://cloud.fermyon.com
Authentication
API Key
Resource Areas
1

Authentication & Security 1

Fermyon payments API declares 1 security scheme for authenticating requests. An API key is passed in the header as Authorization (Bearer). By default, every request must be authenticated.

  • Bearer — JWT Authorization header using the Bearer scheme. Example: "Authorization: Bearer {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.

payments 3
POST
/api/payments/setup-checkout
1 param → 200
GET
/api/payments/customer-portal
1 param → 200
GET
/api/payments/plans
1 param → 200

Schemas 2

The contract defines 2 schemas that model the data the API accepts and returns. The most detailed are PlanItem (2 properties), PaymentIntegrationUrl (1 property). Each schema is shown below with its type and property counts.

PaymentIntegrationUrl
object
1 property
PlanItem
object
2 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

fermyon-payments-api-openapi.yml Raw ↑

Other APIs Fermyon publishes across the network.

Fermyon Wasm Functions
Fermyon accounts API
Fermyon apps API
Fermyon auth-tokens API
Fermyon channels API
Fermyon custom-domains API
Fermyon device-codes API
Fermyon key-value-pairs API
Fermyon key-value-stores API
Fermyon oci API
Fermyon personal-access-tokens API
Fermyon revisions API
Where this information came from

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