Attendance API OpenAPI and Discovery
Summary
Attendance generates Swagger/OpenAPI at runtime but does not commit a generated specification artifact.
Audience
API consumers, developers, QA engineers, architects, and implementation partners.
Reference Content
The service registers endpoint discovery and Swagger generation, then enables Swagger middleware and its UI. Developers should use the approved environment's service discovery documentation to locate the runtime specification; this page intentionally omits internal hosts and ports.
No committed Attendance OpenAPI JSON/YAML artifact was found. No URL API-version segment, API-versioning package registration, version negotiation, or deprecation metadata is present. Minimal API operation names exist for the direct Time Office and foundation operations, while many Attendance routes rely on generated operation discovery. XML documentation generation is not enabled in the service project, so source comments are not confirmed as part of the runtime schema.
The checked-in .http file contains only a basic service request and is not a complete contract suite. It must not be treated as the API specification. A future generated-reference pipeline is an opportunity, not an implemented capability. Do not hand-author or publish a synthetic OpenAPI artifact until runtime output is reviewed for authorization metadata, compatibility shapes, and public-safety concerns.
Source References
microservices/src/attendance-service/Program.csmicroservices/src/attendance-service/attendance-service.httpmicroservices/src/attendance-service/attendance-service.csproj
Related Articles
See Also
Keywords
- Attendance API
- Attendance API OpenAPI and Discovery
Revision Information
- Status: Draft
- Last reviewed: 2026-07-15
- Review cycle: Quarterly