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

Longhorn RecurringJobs API

Recurring job management for scheduling automated snapshot and backup operations on a cron-based schedule. Recurring jobs can be applied to individual volumes or all volumes via groups.

Longhorn RecurringJobs 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 RecurringJobs. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, a GitHub repository, and 1 JSON Schema.

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

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

5 operations 2 paths 4 schemas 1 DELETE2 GET1 POST1 PUT

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
Resource Areas
1

Authentication & Security 1

Longhorn RecurringJobs 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 5

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

RecurringJobs 5

Recurring job management for scheduling automated snapshot and backup operations on a cron-based schedule. Recurring jobs can be applied to individual volumes or all volumes via g…

GET
/v1/recurringjobs
Longhorn List recurring jobs
listRecurringJobs → 200401
POST
/v1/recurringjobs
Longhorn Create a recurring job
createRecurringJob body → 200400401
GET
/v1/recurringjobs/{recurringJobName}
Longhorn Get a recurring job
getRecurringJob 1 param → 200401404
PUT
/v1/recurringjobs/{recurringJobName}
Longhorn Update a recurring job
updateRecurringJob 1 param body → 200400401
DELETE
/v1/recurringjobs/{recurringJobName}
Longhorn Delete a recurring job
deleteRecurringJob 1 param → 204401404

Schemas 4

The contract defines 4 schemas that model the data the API accepts and returns. The most detailed are RecurringJob (8 properties), RecurringJobCreateInput (7 properties), APIError (4 properties), RecurringJobCollection (1 property). Each schema is shown below with its type and property counts.

RecurringJobCollection
object
A collection of recurring job resources.
1 property
RecurringJob
object
A Longhorn recurring job for automated snapshot and backup scheduling.
8 properties
APIError
object
API error response.
4 properties
RecurringJobCreateInput
object
Input for creating or updating a recurring job.
7 properties 4 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

longhorn-recurringjobs-api-openapi.yml Raw ↑

Other APIs Longhorn publishes across the network.

Longhorn BackingImages API
Longhorn Backups API
Longhorn EngineImages API
Longhorn Nodes API
Longhorn Settings API
Longhorn Snapshots API
Longhorn SystemBackups API
Longhorn Volumes API
Where this information came from

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