Revoke an upload reference for the authenticated application
DELETE/v1/storage/files/:fileId
The API key can revoke only its own api_upload reference. Message, template, profile, workspace, calendar and export references are read-only here. If other active catalog references use the same content, the physical object remains available. Otherwise the object is queued for durable deletion; usage is released only after S3 confirms removal. Repeating a successful request is safe. Shared-use counts are limited to the authenticated application. Inventory coverage must be current before revoking the last active catalog reference. Missing, partial or stale coverage returns STORAGE_FILE_INVENTORY_INCOMPLETE; an authorized organization user must finish bounded metadata discovery from the Hub Storage page before retrying. Application API keys cannot start that private refresh. Legacy or retained protected uses return STORAGE_FILE_PROTECTED_USES. Both refusals preserve the reference and do not queue physical deletion.
Request
Responses
- 200
- 401
- 404
- 409
Reference revoked or already revoked.
API key is missing, invalid, expired or unavailable.
STORAGE_FILE_NOT_FOUND; malformed file ID or file outside the authenticated scope.
STORAGE_FILE_NOT_DELETABLE, STORAGE_FILE_DELETE_IN_PROGRESS, STORAGE_FILE_INVENTORY_INCOMPLETE or STORAGE_FILE_PROTECTED_USES. Incomplete inventory or protected uses preserve the reference and do not queue deletion.