Instrument · drive-labels-api

Drive Labels API

An API for managing Drive Labels

An API for managing Drive Labels

---

Public API proxied through Ozma. **Claim this listing** to monetize and manage pricing.

Merit Breakdown

No score data yet

Telemetry

Endpoints

Method	Path	Summary	Price
GET	/v2beta/labels	List labels.	1c
POST	/v2beta/labels	Creates a new Label.	1c
GET	/v2beta/limits/label	Get the constraints on the structure of a Label; such as, the maximum number of Fields allowed and maximum length of the label title.	1c
DELETE	/v2beta/{name}	Deletes a Label's permission. Permissions affect the Label resource as a whole, are not revisioned, and do not require publishing.	1c
GET	/v2beta/{name}	Gets the user capabilities.	1c
POST	/v2beta/{name}:delta	Updates a single Label by applying a set of update requests resulting in a new draft revision. The batch update is all-or-nothing: If any of the update requests are invalid, no changes are applied. The resulting draft revision must be published before the changes may be used with Drive Items.	1c
POST	/v2beta/{name}:disable	Disable a published Label. Disabling a Label will result in a new disabled published revision based on the current published revision. If there is a draft revision, a new disabled draft revision will be created based on the latest draft revision. Older draft revisions will be deleted. Once disabled, a label may be deleted with `DeleteLabel`.	1c
POST	/v2beta/{name}:enable	Enable a disabled Label and restore it to its published state. This will result in a new published revision based on the current disabled published revision. If there is an existing disabled draft revision, a new revision will be created based on that draft and will be enabled.	1c
POST	/v2beta/{name}:publish	Publish all draft changes to the Label. Once published, the Label may not return to its draft state. See `google.apps.drive.labels.v2.Lifecycle` for more information. Publishing a Label will result in a new published revision. All previous draft revisions will be deleted. Previous published revisions will be kept but are subject to automated deletion as needed. Once published, some changes are no longer permitted. Generally, any change that would invalidate or cause new restrictions on existing metadata related to the Label will be rejected. For example, the following changes to a Label will be rejected after the Label is published: * The label cannot be directly deleted. It must be disabled first, then deleted. * Field.FieldType cannot be changed. * Changes to Field validation options cannot reject something that was previously accepted. * Reducing the max entries.	1c
POST	/v2beta/{name}:updateLabelCopyMode	Updates a Label's `CopyMode`. Changes to this policy are not revisioned, do not require publishing, and take effect immediately.	1c
GET	/v2beta/{parent}/locks	Lists the LabelLocks on a Label.	1c
GET	/v2beta/{parent}/permissions	Lists a Label's permissions.	1c
PATCH	/v2beta/{parent}/permissions	Updates a Label's permissions. If a permission for the indicated principal doesn't exist, a new Label Permission is created, otherwise the existing permission is updated. Permissions affect the Label resource as a whole, are not revisioned, and do not require publishing.	1c
POST	/v2beta/{parent}/permissions	Updates a Label's permissions. If a permission for the indicated principal doesn't exist, a new Label Permission is created, otherwise the existing permission is updated. Permissions affect the Label resource as a whole, are not revisioned, and do not require publishing.	1c
POST	/v2beta/{parent}/permissions:batchDelete	Deletes Label permissions. Permissions affect the Label resource as a whole, are not revisioned, and do not require publishing.	1c
POST	/v2beta/{parent}/permissions:batchUpdate	Updates Label permissions. If a permission for the indicated principal doesn't exist, a new Label Permission is created, otherwise the existing permission is updated. Permissions affect the Label resource as a whole, are not revisioned, and do not require publishing.	1c

Quick call

ozma register && ozma call drive-labels-api /v2beta/labels --json

curl -H "Authorization: Bearer $OZMA_KEY" \
  https://gateway.ozma.app/v1/proxy/drive-labels-api/v2beta/labels

# Python
client.proxy_call("drive-labels-api", "/v2beta/labels")

Own this API? Claim the listing to manage pricing and receive payouts.

syncing market data_

Method

Path

Summary

Price

GET

/v2beta/labels

List labels.

POST

/v2beta/labels

Creates a new Label.

GET

/v2beta/limits/label

Get the constraints on the structure of a Label; such as, the maximum number of Fields allowed and maximum length of the label title.

DELETE

/v2beta/{name}

Deletes a Label's permission. Permissions affect the Label resource as a whole, are not revisioned, and do not require publishing.

GET

/v2beta/{name}

Gets the user capabilities.

POST

/v2beta/{name}:delta

Updates a single Label by applying a set of update requests resulting in a new draft revision. The batch update is all-or-nothing: If any of the update requests are invalid, no changes are applied. The resulting draft revision must be published before the changes may be used with Drive Items.

POST

/v2beta/{name}:disable

Disable a published Label. Disabling a Label will result in a new disabled published revision based on the current published revision. If there is a draft revision, a new disabled draft revision will be created based on the latest draft revision. Older draft revisions will be deleted. Once disabled, a label may be deleted with `DeleteLabel`.

POST

/v2beta/{name}:enable

Enable a disabled Label and restore it to its published state. This will result in a new published revision based on the current disabled published revision. If there is an existing disabled draft revision, a new revision will be created based on that draft and will be enabled.

POST

/v2beta/{name}:publish

Publish all draft changes to the Label. Once published, the Label may not return to its draft state. See `google.apps.drive.labels.v2.Lifecycle` for more information. Publishing a Label will result in a new published revision. All previous draft revisions will be deleted. Previous published revisions will be kept but are subject to automated deletion as needed. Once published, some changes are no longer permitted. Generally, any change that would invalidate or cause new restrictions on existing metadata related to the Label will be rejected. For example, the following changes to a Label will be rejected after the Label is published: * The label cannot be directly deleted. It must be disabled first, then deleted. * Field.FieldType cannot be changed. * Changes to Field validation options cannot reject something that was previously accepted. * Reducing the max entries.

POST

/v2beta/{name}:updateLabelCopyMode

Updates a Label's `CopyMode`. Changes to this policy are not revisioned, do not require publishing, and take effect immediately.

GET

/v2beta/{parent}/locks

Lists the LabelLocks on a Label.

GET

/v2beta/{parent}/permissions

Lists a Label's permissions.

PATCH

/v2beta/{parent}/permissions

Updates a Label's permissions. If a permission for the indicated principal doesn't exist, a new Label Permission is created, otherwise the existing permission is updated. Permissions affect the Label resource as a whole, are not revisioned, and do not require publishing.

POST

/v2beta/{parent}/permissions

POST

/v2beta/{parent}/permissions:batchDelete

Deletes Label permissions. Permissions affect the Label resource as a whole, are not revisioned, and do not require publishing.

POST

/v2beta/{parent}/permissions:batchUpdate

Updates Label permissions. If a permission for the indicated principal doesn't exist, a new Label Permission is created, otherwise the existing permission is updated. Permissions affect the Label resource as a whole, are not revisioned, and do not require publishing.