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
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
Longhorn

Longhorn EngineImages API

Engine image management for the Longhorn storage engine. Engine images are OCI images containing the Longhorn engine binary and are used to upgrade or manage storage engine versions.

Documentation Provider Profile APIs.io OpenAPI GitHub

Longhorn EngineImages API is one of 9 APIs that Longhorn publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 1 JSON Schema definition.

Tagged areas include EngineImages. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, a GitHub repository, and 1 JSON Schema.

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

Requests are made against a single base URL, http://{longhornManagerHost}:{longhornManagerPort}.

4 operations 2 paths 3 schemas 1 DELETE2 GET1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.11
Server
http://{longhornManagerHost}:{longhornManagerPort}
Authentication
HTTP Bearer
Contact
Longhorn Community
Resource Areas
1

Authentication & Security 1

Longhorn EngineImages API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (bearerAuth). By default, every request must be authenticated.

  • bearerAuth — Kubernetes service account token for authenticating with the Longhorn Manager API. Typically passed via the Kubernetes API proxy.

Paths & Operations 4

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

EngineImages 4

Engine image management for the Longhorn storage engine. Engine images are OCI images containing the Longhorn engine binary and are used to upgrade or manage storage engine versio…

GET
/v1/engineimages
Longhorn List engine images
listEngineImages → 200401
POST
/v1/engineimages
Longhorn Create an engine image
createEngineImage body → 200400401
GET
/v1/engineimages/{engineImageName}
Longhorn Get an engine image
getEngineImage 1 param → 200401404
DELETE
/v1/engineimages/{engineImageName}
Longhorn Delete an engine image
deleteEngineImage 1 param → 204400401404

Schemas 3

The contract defines 3 schemas that model the data the API accepts and returns. The most detailed are EngineImage (9 properties), APIError (4 properties), EngineImageCollection (1 property). Each schema is shown below with its type and property counts.

APIError
object
API error response.
4 properties
EngineImageCollection
object
A collection of engine image resources.
1 property
EngineImage
object
A Longhorn engine image providing the storage engine binary.
9 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

longhorn-engineimages-api-openapi.yml Raw ↑

Other APIs Longhorn publishes across the network.

Longhorn BackingImages API
AE Profile APIs.io
Longhorn Backups API
AE Profile APIs.io
Longhorn Nodes API
AE Profile APIs.io
Longhorn RecurringJobs API
AE Profile APIs.io
Longhorn Settings API
AE Profile APIs.io
Longhorn Snapshots API
AE Profile APIs.io
Longhorn SystemBackups API
AE Profile APIs.io
Longhorn Volumes API
AE Profile APIs.io
#EngineImages
← Back to L APIs
API Details
ID
longhorn:longhorn-engineimages-api
Server
http://{longhornManagerHost}:{longhornManagerPort}
Docs
https://longhorn.io/docs/
Provider
Longhorn
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=longhorn-engineimages-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/longhorn-engineimages-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

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

Where this information came from

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