StorONE S1 REST API

The S1 REST API manages a StorONE storage system: create and manage applications, volumes, snapshots, shares, file systems and object stores; register hosts and mappings; configure NAS servers, floating IPs and replication; manage nodes, drives and pools; read live and historical capacity, performance, utilization and health monitoring; and configure notification targets. Authentication is a session token obtained from POST /login and sent in the Authorization header. Because S1 is customer-deployed software, the base URL is the address of one of the customer's own S1 controller nodes.

Work with this as data

Every API 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 apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • 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 API
curl "https://apis.io/api/v1/apis/storone-s1-rest-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no email required.

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

API entry from apis.yml

apis.yml Raw ↑
aid: storone-s1-rest-api
name: StorONE S1 REST API
description: 'The S1 REST API manages a StorONE storage system: create and manage applications, volumes,
  snapshots, shares, file systems and object stores; register hosts and mappings; configure NAS servers,
  floating IPs and replication; manage nodes, drives and pools; read live and historical capacity, performance,
  utilization and health monitoring; and configure notification targets. Authentication is a session token
  obtained from POST /login and sent in the Authorization header. Because S1 is customer-deployed software,
  the base URL is the address of one of the customer''s own S1 controller nodes.'
humanURL: https://docs.onestor.com/books/rest-api
baseURL: https://{s1-controller-node}
tags:
- Storage
- Block Storage
- File Storage
- Object Storage
- Replication
- Monitoring
properties:
- type: Documentation
  url: https://docs.onestor.com/books/rest-api
- type: APIReference
  url: https://docs.onestor.com/books/rest-api/chapter/api-reference-guide
- type: GettingStarted
  url: https://docs.onestor.com/books/rest-api/chapter/examples
- type: Authentication
  url: authentication/storone-authentication.yml
x-base-url-note: 'S1 is customer-deployed software: the API is served by the customer''s own S1 controller
  nodes over TCP, and StorONE operates no hosted API endpoint. The base URL is therefore templated by
  necessity, not by omission. StorONE''s own published examples use https://s1-node1.example.com/ and
  s1-n1.example.com as placeholders for the same reason. Probed 2026-08-29: no StorONE-operated API host
  exists to name.'