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

Misskey drive API

The drive API from Misskey — 18 operation(s) for drive.

Misskey drive API is one of 32 APIs that Misskey publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Drives. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, authentication docs, a GitHub repository, and rate-limit docs.

This API exposes 18 operations across 18 paths, and defines 5 schemas. It is described by OpenAPI 3.2.0, at version 2025.4.1-io.12b-fb6fbea074.

Requests are made against a single base URL, https://misskey.io/api.

18 operations 18 paths 5 schemas 18 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2025.4.1-io.12b-fb6fbea074
Server
https://misskey.io/api
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

Misskey drive API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (bearerAuth).

Paths & Operations 18

Across 18 paths, the API surfaces 18 operations — 18 POST. Each is listed below with its method, path, parameters, and response codes.

drive 18
POST
/drive
drive
post___drive → 200400401403418500
POST
/drive/files
drive/files
post___drive___files body → 200400401403418500
POST
/drive/files/attached-notes
drive/files/attached-notes
post___drive___files___attached-notes body → 200400401403418500
POST
/drive/files/check-existence
drive/files/check-existence
post___drive___files___check-existence body → 200400401403418500
POST
/drive/files/create
drive/files/create
post___drive___files___create body → 200400401403418429500
POST
/drive/files/delete
drive/files/delete
post___drive___files___delete body → 204400401403418500
POST
/drive/files/find
drive/files/find
post___drive___files___find body → 200400401403418500
POST
/drive/files/find-by-hash
drive/files/find-by-hash
post___drive___files___find-by-hash body → 200400401403418500
POST
/drive/files/show
drive/files/show
post___drive___files___show body → 200400401403418500
POST
/drive/files/update
drive/files/update
post___drive___files___update body → 200400401403418500
POST
/drive/files/upload-from-url
drive/files/upload-from-url
post___drive___files___upload-from-url body → 204400401403418429500
POST
/drive/folders
drive/folders
post___drive___folders body → 200400401403418500
POST
/drive/folders/create
drive/folders/create
post___drive___folders___create body → 200400401403418429500
POST
/drive/folders/delete
drive/folders/delete
post___drive___folders___delete body → 204400401403418500
POST
/drive/folders/find
drive/folders/find
post___drive___folders___find body → 200400401403418500
POST
/drive/folders/show
drive/folders/show
post___drive___folders___show body → 200400401403418500
POST
/drive/folders/update
drive/folders/update
post___drive___folders___update body → 200400401403418500
POST
/drive/stream
drive/stream
post___drive___stream body → 200400401403418500

Schemas 5

The contract defines 5 schemas that model the data the API accepts and returns. The most detailed are Note (35 properties), DriveFile (17 properties), UserLite (16 properties), DriveFolder (7 properties). Each schema is shown below with its type and property counts.

UserLite
object
16 properties 9 required
Error
object
1 property 1 required
DriveFolder
object
7 properties 4 required
Note
object
35 properties 12 required
DriveFile
object
17 properties 14 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

misskey-drive-api-openapi.yml Raw ↑

Other APIs Misskey publishes across the network.

Misskey account API
Misskey Admin API
Misskey antennas API
Misskey app API
Misskey auth API
Misskey Bubble Game API
Misskey channels API
Misskey charts API
Misskey clip API
Misskey clips API
Misskey Export Custom Emojis API
Misskey federation API
Where this information came from

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