[Issue #7621] Update Opportunity endpoints for two types of auth #7775
+330
−63
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.
Summary
Fixes #7621
Changes proposed
Update the two opportunity retrieval endpoints to support both JWT auth (login.gov) and the new API key auth system:
GET /v1/opportunities/:opportunity_id
GET /v1/opportunities/:legacy_opportunity_id
Context for reviewers
As part of this change, the old/legacy API key authentication method will be deprecated and no longer valid.
The change aligns these endpoints with our broader API authentication strategy while ensuring external API consumers can continue accessing opportunity data through the new API key system.
Validation steps