Asset API Request and Response Models
Named HTTP models
| Direction | DTOs | Endpoint use | Validation owner |
|---|---|---|---|
| Native request | CreateAssetInput, CreateAssetRequestInput, AssignAssetInput, ReturnAssetInput, RejectAssetInput, AssetConditionNoteInput, UploadAssetDocumentInput | Inventory, request, assignment, return, rejection, condition, document upload | Commands and aggregate |
| Native response | AssetDto, AssetAssignmentHistoryDto, AssetDocumentReferenceDto, OpenAssetDto, AssetClearanceStatusDto | Asset detail/list, history, documents, clearance | Explicit mapping and queries |
| Workflow request | WorkflowCallbackDto | Terminal workflow callback | Asset command |
| Compatibility request | MonolithAssetRequest, MonolithAssetStatusUpdate | Legacy save/request/status routes | Compatibility adapter and canonical commands |
There are 15 named HTTP-facing DTOs: 7 native inputs, 5 native outputs, 1 workflow callback, and 2 compatibility inputs. Compatibility responses, health-data, audit, timeline, outbox, deletion messages, and service information use anonymous shapes. Document download returns a file result rather than a JSON DTO.
No example identifiers or business records are published here. DataAnnotations, FluentValidation validators, and generated response-schema declarations were not found.
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/Application/Dtos.csmicroservices/src/asset-service/Application/WorkflowIntegration.csmicroservices/src/asset-service/Application/Compatibility/AssetCompatContracts.cs