Google Drive Labels API
Browse all Google APIs42
AI ReadinessFoundational (D-)42/100
Official vendor OpenAPI document · agent-readyProductivityCollaborationoauth216 EndpointsREST
For Agents
Create, publish, version, and manage taxonomy labels applied to Google Drive files for classification, retention, DLP, and search use cases.
Use for: Create a new 'Confidentiality' label with three selection options, Publish the draft 'Retention Class' label so users can apply it, Disable the legacy 'Project Phase' label without deleting historical applications, List all labels visible to admins in this customer
Not supported: Does not apply labels to specific files, manage Drive content, or enforce DLP rules - use for label taxonomy and lifecycle management only.
The Drive Labels API lets administrators and developers create, publish, and manage labels - structured taxonomies of fields applied to Google Drive files for classification, retention, and search. The API supports the full label lifecycle: create draft labels, attach text, integer, date, user, or selection fields, publish and version them, enable or disable, and delete. Atomic delta operations let multi-field changes apply in a single request, and limits endpoints expose label-system constraints. It is the canonical interface for governance, DLP, and compliance workflows that need machine-readable classifications on Drive content.
Install Jentic One Beta
Connect the Drive Labels API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Drive Labels API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fgoogleapis.com%2Fdrivelabels" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fgoogleapis.com%2Fdrivelabels" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with Drive Labels API.
Create draft labels with text, integer, date, user, or selection fields and a multi-locale title
Apply atomic multi-field changes to a label via the delta endpoint
Publish a draft label so it can be applied to Drive items, then version it for future edits
Disable or enable a published label without deleting it, preserving applied instances
List labels available in the customer with view filtering for admin or end-user contexts
Retrieve label-system limits (max fields, max selection choices) before designing a label
Use Cases
Patterns agents use Drive Labels API for, with concrete tasks.
★ Records and Retention Classification
Records management teams use Drive Labels to apply a 'Retention Class' taxonomy across the organisation, tagging documents with retention durations that downstream tooling enforces. The API lets admins design the label, publish it, and version updates without breaking applied instances. End-to-end rollout is typically days rather than weeks for an in-house solution.
POST /v2/labels with a 'Retention Class' selection field of options 1-year, 3-year, 7-year, then call publish and confirm state == PUBLISHED.
DLP and Confidentiality Tagging
Security teams roll out a 'Confidentiality' label (Public, Internal, Confidential, Restricted) and combine it with Workspace DLP rules so external sharing is blocked on Confidential or Restricted documents. The API drives label creation and updates centrally; the same label IDs can be referenced by DLP policies. New rollouts move from spreadsheets-of-rules to enforced, queryable classifications.
POST /v2/{+name}:delta to add an 'External-share-blocked' selection choice to the existing Confidentiality label, then call publish.
Project and Workflow Tagging
Operations teams attach project, owner, and status fields to documents through Drive Labels so search and reporting can roll up by project even when documents live in different folders. User and date fields make labels first-class metadata for project tracking, and the disable endpoint retires a label without losing the historical attribution on existing files.
Create a 'Project' label with a user field 'Owner' and a selection field 'Status' with options Active, On Hold, Done, then publish it.
Agent-Driven Label Governance via Jentic
An AI agent helping a Workspace admin can propose label schemas, create draft labels, and publish them after review through Jentic. The agent understands the difference between a single delta-update and a publish call because Jentic returns the right operation per intent, with input schemas attached.
Search Jentic for 'create a Drive label', load POST /v2/labels schema, execute with the proposed fields, then call publish on the returned label name.
Key Endpoints
16 endpoints — the drive labels api lets administrators and developers create, publish, and manage labels - structured taxonomies of fields applied to google drive files for classification, retention, and search.
METHOD
PATH
DESCRIPTION
POST
/v2/labels
Create a draft label
GET
/v2/labels
List labels for the customer
POST
/v2/{+name}:delta
Apply atomic multi-field changes to a label
POST
/v2/{+name}:enable
Enable a previously disabled label
POST
/v2/{+name}:disable
Disable a published label without deleting applications
GET
/v2/limits/label
Get label-system limits
POST
/v2/labels
Create a draft label
GET
/v2/labels
List labels for the customer
POST
/v2/{+name}:delta
Apply atomic multi-field changes to a label
POST
/v2/{+name}:enable
Enable a previously disabled label
POST
/v2/{+name}:disable
Disable a published label without deleting applications
GET
/v2/limits/label
Get label-system limits
Jentic AI Readiness Score
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
D
Drive Labels API
- Foundational (D-)42/100
46
Foundational Compliance56
Developer Experience & Jentic Compatibility21
AI-Readiness & Agent Experience94
Agent Usability63
Security62
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
46
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: DSignals: 4
59%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
0%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
25%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
56
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: CSignals: 4
0%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
25%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
21
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: FSignals: 4
82%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
0%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
0%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
94%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
63
Security
Trust, risk posture, and security compliance.
Grade: B-Signals: 1
62%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
62
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: B-Signals: 1
62%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Drive Labels API by hand means standing up Google OAuth2 with the right scopes, targeting drivelabels.googleapis.com, and building the resource-path calls yourself for label taxonomy and lifecycle. Through Jentic you install once, import the Drive Labels API from the API Directory, store the OAuth credential once, and your agent calls it.
Permission scoping
Drive Labels puts the label name in the URL path (/v2/{+name}), so a rule can pin your agent to one label: it can read and apply delta updates to that label and nothing else. You choose the operations it may call, so state-changing ones like enable or disable are not included unless you add them.
Credential isolation
Your Google OAuth credential for Drive Labels is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'list Drive labels' or 'update a label definition', and Jentic returns the matching Drive Labels operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Drive Labels API through Jentic.
What authentication does the Drive Labels API use?
Drive Labels uses Google OAuth 2.0 with the drive.labels or drive.labels.readonly scope, plus drive.admin.labels for admin operations. Through Jentic the credentials live in the encrypted vault and the agent only receives scoped Bearer tokens.
Can I add fields to a published label with the Drive Labels API?
Yes. POST /v2/{+name}:delta accepts a list of update requests including createField. The API increments the label's revision; published versions and applied instances are preserved while new fields appear in the next published version.
What are the rate limits for the Drive Labels API?
Default per-project quota is 600 read requests per minute and 60 write requests per minute. The /v2/limits/label endpoint returns label-system constraints (max fields per label, max selection choices) which are enforced server-side independent of rate limits.
How do I publish a draft label through Jentic?
Search Jentic for 'publish a Drive label', load the schema for POST /v2/{+name}:publish, and execute it with the label resource name. Jentic returns the published label with state == PUBLISHED.
Is the Drive Labels API free?
The API is free to call. Drive Labels itself requires a Google Workspace edition that includes Labels (Business Standard or higher, plus Enterprise editions). Quotas and label limits apply but there is no per-call charge.
How do I disable a label without losing applied data?
POST /v2/{+name}:disable transitions the label to DISABLED. Existing files keep their applied label values for historical audit, but the label cannot be applied to new files until /v2/{+name}:enable is called.
Can I limit what my agent is allowed to do with the Drive Labels API?
Yes. Because your Jentic One instance is self-hosted, your own rules decide which Drive Labels operations and credentials the agent may use. Since the label name sits in the URL path (/v2/{+name}), you can pin the agent to a single label and allow only read and delta-update calls on it. State-changing operations like /v2/{+name}:enable, /v2/{+name}:disable, and :publish stay off limits unless you explicitly grant them.
GET STARTED