Files
OmniRoute/docs/reference
Diego Rodrigues de Sa e Souza bcdf19f422 fix(api): require management auth on the key-issuance limits routes (#19290)
## Summary

- `GET`/`PUT /api/v1/providers/[provider]/limits` and `GET`/`PUT /api/v1/accounts/[id]/limits` now use `requireManagementAuth()`, the guard the neighbouring `/api/v1/registered-keys` and `/api/v1/management/*` routes already use. These caps are what `POST /api/v1/registered-keys` checks before it issues a key, so they take the same credential: a dashboard session, the local CLI token, or an API key with `manage`/`admin` scope. Other keys get `403` through `createErrorResponse()`.
- `POST /api/v1/issues/report` files a GitHub issue with the operator's `GITHUB_ISSUES_TOKEN`, so it now takes the same management credential.
- Allowed response shapes are unchanged. An instance with login disabled stays open, as before.
- `GET /api/v1/quotas/check` keeps its documented Bearer-key access, and a regression test pins it.
- Docs: `docs/openapi.yaml` (plus the matching four entries in `src/app/docs/lib/openapi.generated.ts`), `docs/reference/API_REFERENCE.md` and `docs/security/CORS.md` now list the auth tier for these routes, including `/api/v1/issues/report`.

## Related Issues

- None.

## Target Branch
2026-11-09 09:08:14 -03:00
..
2026-07-13 09:12:40 -03:00