Need help with your APIs? I offer API discovery, governance & evangelism services. Explore services →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

fly-io Volumes API

Operations for managing persistent storage volumes that can be attached to Fly Machines. Volumes provide durable block storage that persists across Machine restarts.

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

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

This API exposes 8 operations across 4 paths, and defines 4 schemas. It is described by OpenAPI 3.1.0, at version 1.0.

Requests are made against 2 base URLs: https://{provider_base_url}, https://api.fly.io.

8 operations 4 paths 4 schemas 1 DELETE3 GET2 POST2 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.0
API Version
1.0
Base URL
https://api.machines.dev
Authentication
HTTP Bearer, HTTP Bearer, API Key
Terms of Service
Resource Areas
1

Authentication & Security 3

fly-io Volumes API declares 3 security schemes for authenticating requests. It accepts HTTP bearer tokens (flySharedSecret). It accepts HTTP bearer tokens (oauthBearerAuth). An API key is passed in the header as X-Fly-Signature (webhookHmac). By default, every request must be authenticated.

  • flySharedSecret — Shared secret provided by Fly.io to the extension provider. Fly.io includes this secret in an Authorization Bearer header on all requests to the provider's API…
  • oauthBearerAuth — Fly.io OAuth access token obtained from the token exchange endpoint.
  • webhookHmac — HMAC-SHA256 signature of the raw request body, computed using the webhook signing secret. Recipients must verify this signature before processing the payload.

Paths & Operations 8

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

Volumes 8

Operations for managing persistent storage volumes that can be attached to Fly Machines. Volumes provide durable block storage that persists across Machine restarts.

GET
/v1/apps/{app_name}/volumes
List volumes in an app
listVolumes 1 param → 200401404
POST
/v1/apps/{app_name}/volumes
Create a volume
createVolume 1 param body → 200400401
GET
/v1/apps/{app_name}/volumes/{volume_id}
Get a volume
getVolume 2 params → 200401404
PUT
/v1/apps/{app_name}/volumes/{volume_id}
Update a volume
updateVolume 2 params body → 200401404
DELETE
/v1/apps/{app_name}/volumes/{volume_id}
Delete a volume
deleteVolume 2 params → 200401404
PUT
/v1/apps/{app_name}/volumes/{volume_id}/extend
Extend a volume
extendVolume 2 params body → 200400401404
GET
/v1/apps/{app_name}/volumes/{volume_id}/snapshots
List volume snapshots
listVolumeSnapshots 2 params → 200401404
POST
/v1/apps/{app_name}/volumes/{volume_id}/snapshots
Create a volume snapshot
createVolumeSnapshot 2 params → 200401404

Schemas 4

The contract defines 4 schemas that model the data the API accepts and returns. The most detailed are Volume (12 properties), CreateVolumeRequest (7 properties), VolumeSnapshot (5 properties), ErrorResponse (2 properties). Each schema is shown below with its type and property counts.

CreateVolumeRequest
object
Request body for creating a new Fly Volume.
7 properties 3 required
ErrorResponse
object
A standard error response returned by the API on failure.
2 properties
Volume
object
A Fly Volume providing persistent block storage for Fly Machines.
12 properties
VolumeSnapshot
object
A point-in-time snapshot of a Fly Volume.
5 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

fly-io-volumes-api-openapi.yml Raw ↑

Other APIs fly-io publishes across the network.

Fly.io Machines API
Fly.io GraphQL API
Fly.io Extensions API
fly-io Apps API
fly-io OAuth API
fly-io SSO API
fly-io Tokens API
fly-io Webhooks API