Fix critical auth: send access-token header instead of Authorization: Bearer#4
Merged
pimfeltkamp merged 1 commit intomainfrom Apr 28, 2026
Merged
Conversation
Critical: every authenticated request was being rejected by the AWS API Gateway in front of api.cryptohopper.com/v1/*. Switching to access-token: <token> as documented in the official Cryptohopper API docs and used by the legacy iOS/Android SDKs. Bump to v0.4.0-alpha.2. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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
1 participant
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.
Tracking: cryptohopper-resources#9. Sister PR to Node #9 and Python #4 — same critical bug, same fix.
The transport sent
Authorization: Bearer <token>which the AWS API Gateway in front ofapi.cryptohopper.com/v1/*rejects with405 Missing Authentication Token(it routesAuthorizationto a SigV4 parser). The Public API v1 usesaccess-token: <token>— confirmed by the live API docs and the legacycryptohopper-ios-sdk/cryptohopper-android-sdk.Changes:
cryptohopper.go:280— header switched, comment addedcryptohopper_test.go—TestRequest_BearerAndUserAgentrenamed toTestRequest_AccessTokenAndUserAgent, assertsaccess-token: ch_testis set andAuthorizationis emptyVersionconstant + CHANGELOG bumped tov0.4.0-alpha.2No public-API change.