Asset API Summary
Summary
Epic 13.3 verified 31 method/route pairs across the asset-service. This page groups them by purpose so readers can orient quickly; it does not re-list every pair. For the full catalog with methods, paths, and payloads, follow the cross-links to the authoritative API documentation.
Audience
Developers and QA engineers integrating with the service, support engineers tracing a call, and solution architects assessing the surface area.
Reference Content
Endpoint groups
| Group | Purpose | Path family |
|---|---|---|
| Native asset | Create, list, detail, update, and status changes for assets. | /asset/* |
| Assignment | Assign an asset and record assignment. | /asset/* |
| Request and approval | Raise a request and drive approval (direct or managed). | /asset/* |
| Documents | Attach, list, download, and remove document references. | /asset/* |
| Workflow | Idempotent inbound workflow callback. | /asset/* |
| Compatibility | Monolith-shaped HR Operations surface. | /api/hr-operations/* |
| Health and foundation | Health, service info, health-data, and outbox inspection. | /health, service-info, /asset/* |
Native endpoints live under /asset/*; the compatibility surface mirrors the legacy shape under /api/hr-operations/*. The two surfaces coexist during the transitional period.
Authorization posture
Native and compatibility endpoints are anonymous and tenant-scoped rather than role-authorized. Tenant context is required, and self-service reads are narrowed to the caller's labor id at the gateway. See the Permissions Matrix for the per-action breakdown.
Source References
microservices/src/asset-service/Api/AssetEndpoints.csmicroservices/src/asset-service/Api/AssetCompatEndpoints.csmicroservices/src/asset-service/Application/Commands/AssetCommands.cs
Related Articles
See Also
Keywords
asset api, endpoints, compatibility, native surface, tenant-scoped
Revision Information
- Status: Draft
- Last reviewed: 2026-07-17
- Review cycle: Quarterly