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

CubeFS Multipart API

Multipart upload operations for uploading large objects in parts. Supports initiating, uploading parts, listing parts, completing, and aborting multipart uploads.

CubeFS Multipart API is one of 11 APIs that CubeFS publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 1 JSON Schema definition.

Tagged areas include Multipart. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, a GitHub repository, and 1 JSON Schema.

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

Requests are made against a single base URL, http://{objectNodeHost}:{objectNodePort}.

4 operations 2 paths 5 schemas 1 DELETE2 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
3.3
Server
http://{objectNodeHost}:{objectNodePort}
Authentication
API Key
Resource Areas
1

Authentication & Security 1

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

  • awsAuth — AWS Signature Version 4 authorization. Format: AWS4-HMAC-SHA256 Credential={accessKey}/{date}/{region}/s3/aws4request, SignedHeaders={headers}, Signature={sign…

Paths & Operations 4

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

Multipart 4

Multipart upload operations for uploading large objects in parts. Supports initiating, uploading parts, listing parts, completing, and aborting multipart uploads.

POST
/{bucket}/{key}?uploads
CubeFS Initiate a multipart upload
createMultipartUpload 2 params → 200400401
PUT
/{bucket}/{key}?uploadId={uploadId}
CubeFS Upload a part
uploadPart 4 params body → 200400401
POST
/{bucket}/{key}?uploadId={uploadId}
CubeFS Complete a multipart upload
completeMultipartUpload 3 params body → 200400401
DELETE
/{bucket}/{key}?uploadId={uploadId}
CubeFS Abort a multipart upload
abortMultipartUpload 3 params → 204401404

Schemas 5

The contract defines 5 schemas that model the data the API accepts and returns. The most detailed are CompleteMultipartUploadResult (4 properties), S3Error (4 properties), InitiateMultipartUploadResult (3 properties), CompletedPart (2 properties). Each schema is shown below with its type and property counts.

S3Error
object
S3-compatible error response in XML format.
4 properties
CompleteMultipartUpload
object
Request body for completing a multipart upload.
1 property
InitiateMultipartUploadResult
object
Result of initiating a multipart upload.
3 properties
CompletedPart
object
A part to include when completing a multipart upload.
2 properties 2 required
CompleteMultipartUploadResult
object
Result of completing a multipart upload.
4 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

cubefs-multipart-api-openapi.yml Raw ↑

Other APIs CubeFS publishes across the network.

CubeFS ACLs API
CubeFS Buckets API
CubeFS Cluster API
CubeFS DataNodes API
CubeFS DataPartitions API
CubeFS MetaNodes API
CubeFS MetaPartitions API
CubeFS Objects API
CubeFS Users API
CubeFS Volumes API
Where this information came from

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