Fermyon · OpenAPI Overlay 1.0.0

API Evangelist enhancements — Fermyon channels-api API

12 actions 12 updates documentation extends fermyon-channels-api-openapi.yml
Derived by API Evangelist Built from the contracts Fermyon publishes. Fermyon did not publish this file.
View Overlay File View on GitHub Overlay Specification

What the actions change

operationIdcontactexternalDocs

Targets 12

$.paths['/api/channels'].get
$.paths['/api/channels'].post
$.paths['/api/channels/{id}'].get
$.paths['/api/channels/{id}'].put
$.paths['/api/channels/{id}'].patch
$.paths['/api/channels/{id}'].delete
$.paths['/api/channels/{channelId}/desired-status'].put
$.paths['/api/channels/{id}/logs'].get
$.paths['/api/channels/{id}/logs/raw'].get
$.paths['/api/channels/{id}/healthz'].get
$.info
$

OpenAPI Overlay

Raw ↑
overlay: 1.0.0
info:
  title: API Evangelist enhancements — Fermyon channels-api API
  version: 1.0.0
extends: fermyon-channels-api-openapi.yml
x-generated: '2026-09-09'
x-method: generated
x-source: API Evangelist enrichment pipeline; targets openapi/fermyon-channels-api-openapi.yml
x-note: Fermyon publishes the Cloud API contract without a single operationId (verified against https://raw.githubusercontent.com/fermyon/cloud-openapi/main/swagger.json
  on 2026-09-09). These operationIds are computed deterministically from HTTP method + path by API Evangelist and
  are NOT names Fermyon publishes. They are kept in this overlay rather than written into the spec so the provider
  contract stays unmodified.
actions:
- target: $.paths['/api/channels'].get
  description: Add a stable operationId for GET /api/channels; the published contract declares none.
  update:
    operationId: getChannels
- target: $.paths['/api/channels'].post
  description: Add a stable operationId for POST /api/channels; the published contract declares none.
  update:
    operationId: createChannels
- target: $.paths['/api/channels/{id}'].get
  description: Add a stable operationId for GET /api/channels/{id}; the published contract declares none.
  update:
    operationId: getChannelsById
- target: $.paths['/api/channels/{id}'].put
  description: Add a stable operationId for PUT /api/channels/{id}; the published contract declares none.
  update:
    operationId: replaceChannelsById
- target: $.paths['/api/channels/{id}'].patch
  description: Add a stable operationId for PATCH /api/channels/{id}; the published contract declares none.
  update:
    operationId: updateChannelsById
- target: $.paths['/api/channels/{id}'].delete
  description: Add a stable operationId for DELETE /api/channels/{id}; the published contract declares none.
  update:
    operationId: deleteChannelsById
- target: $.paths['/api/channels/{channelId}/desired-status'].put
  description: Add a stable operationId for PUT /api/channels/{channelId}/desired-status; the published contract
    declares none.
  update:
    operationId: replaceChannelsByChannelidDesiredStatus
- target: $.paths['/api/channels/{id}/logs'].get
  description: Add a stable operationId for GET /api/channels/{id}/logs; the published contract declares none.
  update:
    operationId: getChannelsByIdLogs
- target: $.paths['/api/channels/{id}/logs/raw'].get
  description: Add a stable operationId for GET /api/channels/{id}/logs/raw; the published contract declares none.
  update:
    operationId: getChannelsByIdLogsRaw
- target: $.paths['/api/channels/{id}/healthz'].get
  description: Add a stable operationId for GET /api/channels/{id}/healthz; the published contract declares none.
  update:
    operationId: getChannelsByIdHealthz
- target: $.info
  description: Attach the provider documentation and contract source that the published document omits.
  update:
    contact:
      name: Fermyon Cloud documentation
      url: https://developer.fermyon.com/cloud/index
- target: $
  description: Attach externalDocs pointing at the Fermyon Cloud REST API reference page.
  update:
    externalDocs:
      description: Fermyon Cloud REST API reference
      url: https://developer.fermyon.com/cloud/rest-api

Work with this as data

Every overlay here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for openapi overlays

4 MCP tools reach this
  • find_overlaysBrowse and filter every overlay in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This overlay
curl "https://apis.io/api/v1/overlays/fermyon-channels-api-overlay"
All openapi overlays
curl "https://apis.io/api/v1/overlays?limit=25"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.