feat: api key feature - #48
Merged
Merged
Conversation
rivon0507
force-pushed
the
feat/api-key
branch
from
February 19, 2026 15:54
060b1d8 to
e89ec95
Compare
Ryan2486
previously approved these changes
Feb 20, 2026
rivon0507
force-pushed
the
feat/api-key
branch
from
February 20, 2026 10:04
2fc62d9 to
f1a3bed
Compare
Ryan2486
approved these changes
Feb 20, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This pull request introduces a comprehensive API key management system and standardizes API route prefixes across the application. It also restructures authentication and security configuration to support partner API key authentication. The key changes are grouped below.
API Key Management Feature:
ApiKeyControllerand associated DTOs (ApiKeyCreateRequest,ApiKeyResponse,ApiKeyWithRawToken). These endpoints are restricted to superadmins. [1] [2] [3] [4]ApiKeyMapperfor mapping between API key entities and DTOs, supporting both standard and raw token responses.Security and Authentication Configuration:
SecurityConfigurationto add a dedicated security filter chain for partner API endpoints (/integration/**), using a newApiKeyAuthenticationFilterfor API key authentication. The main application endpoints now useJwtAuthenticationFilterinstead of the previousAppAuthenticationFilter. [1] [2] [3] [4]AuthPropertiesto group session and API key settings into nested records, improving configuration structure and clarity. [1] [2]API Route Standardization:
/api/v1/prefix for their endpoints, improving consistency and future-proofing the API. Integration endpoints are also grouped under/integration/. [1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] [12]These changes collectively enable secure partner integrations, enhance API management for administrators, and lay the groundwork for consistent API versioning.