Skip to main content
Version: Latest

Storage

Upload, inspect and revoke application files using verified storage reuse.

📄️List the scoped unified storage inventory

Reads the persisted metadata index without scanning source tables or contacting S3. Results include legacy source evidence, nullable sizes, coverage and scoped usage counts. Source permissions and application scope apply before items, details and summaries are returned. Shared objects do not grant access to another application or source. Retained uses remain protected. An authorized media URL is returned only for active ready catalog references; bucket, object key, contact data and message content are not returned. Coverage and signed differences do not identify proven orphans, verified duplicates or billing errors; counters and billing are not corrected by this read. Stored objects and unresolved owned-media evidence are listed; external URL-only references, including workspace URL imports, remain internal discovery evidence and are omitted from list, detail and summary totals. External links do not consume platform storage merely because their URLs are recorded.

📄️Read one inventory item and its scoped source uses

Returns one visible indexed item and a bounded page of its authorized source uses. Reads the persisted metadata index without scanning source tables or contacting S3. Results include legacy source evidence, nullable sizes, coverage and scoped usage counts. Source permissions and application scope apply before items, details and summaries are returned. Shared objects do not grant access to another application or source. Retained uses remain protected. Authorized media URLs are available only for active ready catalog references; bucket, object key, contact data and message content are not returned. Coverage and signed differences do not identify proven orphans, verified duplicates or billing errors; counters and billing are not corrected by this read. Stored objects and unresolved owned-media evidence are listed; external URL-only references, including workspace URL imports, remain internal discovery evidence and are omitted from list, detail and summary totals. External links do not consume platform storage merely because their URLs are recorded.

📄️Upload a file to the authenticated application's storage

Upload one file using multipart/form-data and a required Idempotency-Key. The API key determines the application and organization. Additional multipart fields, including organization, application and S3 location, are rejected. Content is deduplicated by verified SHA-256 within an organization; new references to existing bytes do not increase physical storage usage. Exact retries with the same key return the original reference; changing the file or filename conflicts. The returned media URL serves the file as an attachment. Generic upload does not guarantee that a communication channel accepts the file media type or size.

📄️Revoke an upload reference for the authenticated application

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.