MicroCeph REST API

MicroCeph is Canonical's opinionated, snap-delivered Ceph distribution. It publishes a small OpenAPI 3.1.0 contract for its cluster REST surface. Recorded here because it is a real published first-party contract, but it is thin — one path and two operations — and most MicroCeph operation is through the CLI.

Operations 2

PUT /1.0/microceph/config/log-level Set log level for MicroCeph #
GET /1.0/microceph/config/log-level Get log level for MicroCeph #

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/microceph-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 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.

OpenAPI Specification

canonical-microceph-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  version: '1.0'
  title: REST Microceph API
tags:
- name: Microceph
paths:
  /1.0/microceph/config/log-level:
    put:
      summary: Set log level for MicroCeph
      description: Allows the client to configure the logging levels for the MicroCeph daemon.
      operationId: setLogLevel
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/Level'
      responses:
        '200':
          description: Successfully set log-level
        default:
          description: Default error response
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Response'
      tags:
      - Microceph
    get:
      summary: Get log level for MicroCeph
      description: Fetches the current logging level of the MicroCeph daemon.
      operationId: getLogLevel
      responses:
        '200':
          description: Successfully fetched log-level
          content:
            application/json:
              schema:
                type: object
                properties:
                  metadata:
                    type: integer
                    description: Numerical value of the log-level
                    $ref: '#/components/schemas/Level'
                    example: 4
        default:
          description: Default error response
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Response'
      tags:
      - Microceph
components:
  schemas:
    Level:
      type: string
      oneOf:
      - title: PANIC
        const: 0
      - title: FATAL
        const: 1
      - title: ERROR
        const: 2
      - title: WARNING
        const: 3
      - title: INFO
        const: 4
      - title: DEBUG
        const: 5
      - title: TRACE
        const: 6
    Response:
      type: object
      properties:
        type:
          type: string
          description: Type of response
          examples:
          - sync
          - error
        status:
          type: string
          description: Status of operation.
          examples:
          - Success
          - Error
        status_code:
          type: integer
          description: Success HTTP status code, 0 for errors.
          examples:
          - 200
          - 0
        operation:
          type: string
          description: Operation name.
        error_code:
          type: string
          description: Error HTTP status code, 0 for success.
        error:
          type: string
          description: Description of error.
          example: 'Failed to run: ceph config get test_key: exit status 22'
        metadata:
          oneOf:
          - type: object
          - type: 'null'
          description: Response payload, could be null, or a valid json object.