fix: wire JWT bearer auth into the typed API client - #439
Merged
kilodesodiq-arch merged 2 commits intoAug 20, 2026
Conversation
The api-client attached no auth header and documented the obsolete x-api-key model. Every request to a JWT-protected endpoint failed with 401 unless callers manually rolled token attachment. This adds a token-store (setToken/getToken), a token-aware fetch wrapper that attaches Authorization: Bearer <token> on every request, and a single-flight refresh-on-401 path. The stale x-api-key comment is replaced with JWT guidance. Closes ChainForgee#433
… failure The @sentry/nextjs package is not installed as a dependency but was imported in the error boundary component, causing TS2307 type-check failure in Frontend CI.
4 tasks
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.
Summary
The api-client attached no auth header and documented the obsolete x-api-key model. Every request to a JWT-protected endpoint failed with 401 unless callers manually rolled token attachment.
This adds a token-store (setToken/getToken), a token-aware fetch wrapper that attaches Authorization: Bearer on every request, and a single-flight refresh-on-401 path. The stale x-api-key comment is replaced with JWT guidance.
Closes #433
Testing
Checklist