Performance API Overview
Summary
Source-backed overview of the Performance minimal-API surface.
Audience
API consumers, engineers, architects, QA, support, security reviewers, implementation partners, and product owners.
Overview
Performance exposes native operations under the /performance family and legacy-shaped operations under /api/hr-operations. Endpoint modules are registered directly at startup; no MVC Controllers are present.
Endpoint family
| Family | Route | Methods | Contract or purpose |
|---|---|---|---|
| Native | /performance | GET and POST | Cycles, appraisals, Workflow, reports, and diagnostics |
| Compatibility | /api/hr-operations/performance | GET, POST, DELETE | Flat legacy-shaped resource |
| Workspace | /api/hr-operations/workspace | GET | Legacy workspace projection |
- Native commands use application Result mapping; direct queries return arrays, DTOs, or small message objects.
- Global service health and discovery are also mapped at startup.
- Authentication middleware is active, but no Performance endpoint declares an authorization requirement.
Classification
Transitional because native and compatibility APIs coexist and endpoint authorization is not enforced.
Authentication and authorization
Bearer authentication and tenant context are registered. No Performance endpoint in this family declares an authorization requirement unless explicitly stated above.
Requires confirmation
Public route ownership, authorization policy, compatibility retirement, API lifecycle policy, and consumer support commitments require confirmation.
Diagram
Related Articles
See Also
Keywords
- Performance API
- API Overview
- Draft API documentation
Source References
microservices/src/performance-service/Program.csmicroservices/src/performance-service/Api/PerformanceEndpoints.csmicroservices/src/performance-service/Api/PerformanceCompatEndpoints.cs
Revision Information
- Status: Draft
- Last reviewed: 2026-07-16
- Review cycle: Quarterly