# Internal Swagger

This portal aggregates service OpenAPI specs, but individual service Swagger
generators should remain close to the code.

## Current Status

- `service-api-account-alias` already wires Nest Swagger and serves docs when
  Swagger is enabled.
- `service-payment-gateway` includes L5 Swagger configuration and generated JSON
  or YAML under its configured docs route.
- `service-core-api` and `service-api-mobile` currently expose controllers but
  do not appear to wire Swagger generation yet.

## Next Implementation Move

Wire Swagger/OpenAPI in `service-core-api` and `service-api-mobile`, then add CI
jobs that export their generated specs into this portal. The portal should fail
builds when a referenced OpenAPI file is invalid.

## Publication Rule

Internal specs can show operational endpoints. Partner docs should only publish
the scoped partner contract. When in doubt, split internal and partner OpenAPI
files instead of hiding sensitive routes with prose.