Asset Management API Documentation

Summary

Asset Service exposes 31 verified HTTP operations across native, compatibility, and host-foundation registration surfaces. The API uses ASP.NET Core 8 minimal APIs; no controllers were found.

Audience

Developers, QA and support engineers, implementation partners, architects, and security reviewers responsible for Asset Management HTTP contracts.

Overview

This section documents the complete verified Asset Service API surface, its request and response models, security and tenant behavior, validation, compatibility boundaries, errors, discovery, and test evidence.

Verified registration surfaces

Surface	Operations
Native /asset group	23
Compatibility routes	6
Host foundation	2
Total	31

Swagger middleware is not counted as an operation. Gateway proxy and ESS composition routes are documented as routing boundaries, not counted again as Asset Service endpoints.

Documentation map

The section covers architecture, security, tenant context, models, validation, capability APIs, errors, OpenAPI, testing, the authoritative endpoint catalog, and limitations.

Authentication and authorization middleware are registered, but no Asset endpoint requires authorization metadata. All pages remain Draft.

Related Articles

• Asset Management
• Technical documentation
• Business documentation

See Also

• Endpoint catalog
• API limitations

Keywords

• Asset Management API
• Asset Service endpoints
• Compatibility API

Revision Information

• Status: Draft
• Last reviewed: 2026-07-17
• Review cycle: Quarterly

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/Program.cs
• microservices/src/asset-service/Api/AssetEndpoints.cs
• microservices/src/asset-service/Api/AssetCompatEndpoints.cs
• microservices/src/gateway-api/Program.cs