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

OpenMetadata Drive Services API

`Drive Service` is a cloud file storage service such as Google Drive, OneDrive, SharePoint, Box, or Dropbox where documents, spreadsheets, and other files are stored.

OpenMetadata Drive Services API is one of 89 APIs that OpenMetadata publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Drive Services. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and authentication docs.

This API exposes 18 operations across 14 paths, and defines 30 schemas. It is described by OpenAPI 3.0.1, at version 1.13.

Requests are made against 2 base URLs: /api, http://localhost:8585/api.

18 operations 14 paths 30 schemas 4 DELETE7 GET1 PATCH1 POST5 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.1
API Version
1.13
Base URL
https://{your-host}/api/v1
Authentication
HTTP Bearer
License
Resource Areas
1

Authentication & Security 1

OpenMetadata Drive Services API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (JWT) (BearerAuth). By default, every request must be authenticated.

Paths & Operations 18

Across 14 paths, the API surfaces 18 operations — 4 DELETE, 7 GET, 1 PATCH, 1 POST, 5 PUT. Each is listed below with its method, path, parameters, and response codes.

Drive Services 18

Drive Service is a cloud file storage service such as Google Drive, OneDrive, SharePoint, Box, or Dropbox where documents, spreadsheets, and other files are stored.

PUT
/v1/services/driveServices/{id}/followers
Add a follower
addFollowerToDriveService 1 param body → 200404
PUT
/v1/services/driveServices/{id}/testConnectionResult
Add test connection result
addTestConnectionResult_3 1 param body → 200
GET
/v1/services/driveServices
List drive services
listDriveServices 6 params → 200
PUT
/v1/services/driveServices
Update drive service
createOrUpdateDriveService body → 200400
POST
/v1/services/driveServices
Create a drive service
createDriveService body → 200400
DELETE
/v1/services/driveServices/name/{name}
Delete a drive service by name
deleteDriveServiceByName 3 params → 200404
GET
/v1/services/driveServices/{id}
Get a drive service
getDriveServiceByID 4 params → 200404
DELETE
/v1/services/driveServices/{id}
Delete a drive service by Id
deleteDriveService 3 params → 200404
PATCH
/v1/services/driveServices/{id}
Update a drive service
patchDriveService 1 param body → default
DELETE
/v1/services/driveServices/async/{id}
Asynchronously delete a drive service by Id
deleteDriveServiceAsync 3 params → 200404
DELETE
/v1/services/driveServices/{id}/followers/{userId}
Remove a follower
deleteFollowerFromDriveService 2 params → 200
GET
/v1/services/driveServices/name/{name}/export
Export drive service in CSV format
exportDriveService 2 params → 200
GET
/v1/services/driveServices/name/{fqn}
Get a drive service by name
getDriveServiceByFQN 4 params → 200404
GET
/v1/services/driveServices/{id}/versions/{version}
Get a version of the drive service
getSpecificDriveServiceVersion 2 params → 200404
PUT
/v1/services/driveServices/name/{name}/import
Import service from CSV to update drive service (no creation allowed)
importDriveService 3 params body → 200
GET
/v1/services/driveServices/history
List all entity versions within a time range
listAllEntityVersionsByTimestamp_43 5 params → 200
GET
/v1/services/driveServices/{id}/versions
List drive service versions
listAllDriveServiceVersion 1 param → 200
PUT
/v1/services/driveServices/restore
Restore a soft deleted drive service
restore_33 body → 200

Schemas 30

The contract defines 30 schemas that model the data the API accepts and returns. The most detailed are DriveService (36 properties), ChangeEvent (14 properties), TagLabel (13 properties), CreateDriveService (13 properties). Each schema is shown below with its type and property counts.

TagLabelRecognizerMetadata
object
5 properties 3 required
ChangeSummaryMap
object
AccessDetails
object
3 properties 1 required
RestoreEntity
object
1 property 1 required
CoverImage
object
2 properties
FieldChange
object
3 properties
LifeCycle
object
3 properties
EntityHistory
object
2 properties 2 required
AssetCertification
object
3 properties 3 required
ResultList
object
5 properties 1 required
Paging
object
5 properties 1 required
TestConnectionResult
object
3 properties 1 required
JsonPatch
object
ChangeDescription
object
5 properties
DriveConnection
object
1 property
ChangeEvent
object
14 properties 5 required
UsageStats
object
2 properties 1 required
Style
object
3 properties
Votes
object
4 properties
CsvImportResult
object
7 properties
TagLabel
object
13 properties 4 required
PatternMatch
object
3 properties 2 required
TagLabelMetadata
object
2 properties
EntityError
object
2 properties
DriveService
object
36 properties 3 required
TestConnectionStepResult
object
5 properties 3 required
CreateDriveService
object
13 properties 2 required
DriveServiceList
object
5 properties 1 required
EntityReference
object
9 properties 2 required
UsageDetails
object
4 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

openmetadata-drive-services-api-openapi.yml Raw ↑

Other APIs OpenMetadata publishes across the network.

OpenMetadata Agent Executions API
OpenMetadata AI Applications API
OpenMetadata AI Governance Policies API
OpenMetadata API Collections API
OpenMetadata API Endpoint API
OpenMetadata API Services API
OpenMetadata Apps API
OpenMetadata Audit Logs API
OpenMetadata Bots API
OpenMetadata ChangeSummary API
OpenMetadata Charts API
OpenMetadata Classifications API
Where this information came from

This is an independent, third-party profile of OpenMetadata Drive Services 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.