Asset Approval API
Approval behavior
Asset Service does not expose a direct native approve route. Manual approval is represented by assignment of an eligible request. Native rejection uses POST /asset/assets/{asset}/reject with RejectAssetInput. Workflow-managed requests reject direct assign/reject attempts with conflict; terminal decisions arrive through the callback API.
Duplicate callbacks for an already-decided request succeed without reapplying events. Callback state mismatch can conflict. Approval task APIs, approver policy, escalation, callback authorization, and retry endpoints are Not implemented in Asset Service.
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/AssetCommands.csmicroservices/src/asset-service/Application/WorkflowIntegration.cs