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

Rook Objects API

S3-compatible object upload, download, listing, deletion, and metadata operations within Ceph Object Storage buckets

Rook Objects API is one of 6 APIs that Rook publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 2 JSON Schema definitions.

Tagged areas include Objects. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, and 2 JSON Schemas.

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

Requests are made against a single base URL, http://{rgw-host}:{port}.

5 operations 2 paths 3 schemas 1 DELETE2 GET1 HEAD1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Server
http://{rgw-host}:{port}
Authentication
API Key
Terms of Service
Resource Areas
1

Authentication & Security 1

Rook Objects API declares 1 security scheme for authenticating requests. An API key is passed in the header as Authorization (s3Auth). By default, every request must be authenticated.

  • s3Auth — AWS Signature Version 4 (SigV4) or AWS Signature Version 2 authentication using access key and secret key pairs provisioned by CephObjectStoreUser Kubernetes C…

Paths & Operations 5

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

Objects 5

S3-compatible object upload, download, listing, deletion, and metadata operations within Ceph Object Storage buckets

GET
/{bucket}
List Objects in a Bucket
listObjects 7 params → 200404
PUT
/{bucket}/{key}
Upload an Object
putObject 2 params body → 200400404
GET
/{bucket}/{key}
Download an Object
getObject 5 params → 200206304404
HEAD
/{bucket}/{key}
Get Object Metadata
headObject 2 params → 200404
DELETE
/{bucket}/{key}
Delete an Object
deleteObject 2 params → 204404

Schemas 3

The contract defines 3 schemas that model the data the API accepts and returns. The most detailed are ListBucketResult (8 properties), Object (6 properties), ErrorResponse (4 properties). Each schema is shown below with its type and property counts.

ListBucketResult
object
Response to a list objects request for a bucket
8 properties
Object
object
An S3 object stored in a Ceph Object Storage bucket
6 properties
ErrorResponse
object
S3-compatible error response returned when an operation fails
4 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

rook-objects-api-openapi.yml Raw ↑

Other APIs Rook publishes across the network.

Rook Ceph Custom Resource API
Rook Ceph Block Storage API
Rook Ceph Shared Filesystem API
Rook Buckets API
Rook Multipart Uploads API
Where this information came from

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