← API referenceAccess · API access unavailable
API REFERENCE / ACCESS
DELETE /v1/grants/{grant_id}
Revoke an integration’s folder grant.
Request fields
| Location | Field | Type | Required | Description |
|---|---|---|---|---|
| Header | Authorization | string | Yes | Credential scoped to the authorized resource. |
| Path | grant_id | string | Yes | Grant managed by the account owner. |
Request example
Example request
DELETE /v1/grants/grant_123
Authorization: Bearer <owner token>HTTP status codes
| Status | Meaning |
|---|---|
204 No Content | Success response shown below. |
401 Unauthorized | Missing, expired, or invalid credential. |
403 Forbidden | Credential is valid but lacks the required scope or role. |
404 Not Found | Grant is not visible to this owner. |
429 Too Many Requests | Rate limit reached; honor Retry-After when provided. |
503 Service Unavailable | Service temporarily unavailable; retry safely. |
Response fields
| Field | Type | Example |
|---|---|---|
body | none | No response body |
Response example
Example response
204 No ContentHow it works
New metadata and byte reads must be denied immediately at the API boundary. Offline replicas remove their local projection on reconnect; already-exported bytes cannot be remotely recalled.