Asset Document API
Document flow
| Method and route | Behavior | Verified outcomes |
|---|---|---|
POST /asset/assets/{asset}/documents | Validate/decode content, store bytes externally, persist local reference | Created, bad request, not found, service unavailable |
GET /asset/assets/{asset}/documents | List local references | Success or not found |
GET /asset/assets/{asset}/documents/{document}/download | Resolve local reference and stream externally owned bytes | File, not found, or service unavailable |
DELETE /asset/assets/{asset}/documents/{document} | Remove local reference only | Success or not found |
Asset Service owns association metadata; Document Service owns bytes. Removal retains external storage. Versioning, replacement, external deletion, malware-scanning evidence, retention actions, and document-specific authorization are Not implemented.
Classification
The API is Transitional. Capabilities explicitly described as absent are Not implemented. Host diagnostics and evidence routes are Foundation. Production exposure, ownership, and governance Require confirmation.
Source References
microservices/src/asset-service/Api/AssetEndpoints.csmicroservices/src/asset-service/Application/Commands/DocumentCommands.csmicroservices/src/asset-service/Application/DocumentIntegration.csmicroservices/src/asset-service/Infrastructure/AssetDocumentGateway.cs