Repository navigation
feat(client): send the API key in the X-API-Key header - #38
Merged
Merged
Conversation
fetchQuote no longer puts apiKey in the URL, and fetchSwapTransactions no longer puts it in the POST body: both send it in the X-API-Key header, keeping it out of server logs, browser history and caches. The Haystack Router refuses secret (hay_sk_) keys in the URL. The logger also redacts an X-API-Key header.
txnlab-release-bot Bot
added a commit
that referenced
this pull request
Nov 1, 2026
# [3.3.0](v3.2.0...v3.3.0) (2026-11-01) ### Features * **client:** send the API key in the X-API-Key header ([#38](#38)) ([d4fc2a4](d4fc2a4))
Contributor
|
🎉 This PR is included in version 3.3.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
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
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.
fetchQuote no longer puts
apiKeyin the URL, and fetchSwapTransactions no longer puts it in the POST body: both send it in theX-API-Keyheader, keeping it out of server logs, browser history and caches. The Haystack Router refuses secret (hay_sk_) keys in the URL. The logger also redacts anX-API-Keyheader.The router accepts the header and allows it in CORS preflights since haystack-router f74b3d2, live on mainnet (checked: a quote with the key only in the header returns 200, and an OPTIONS preflight for
x-api-keyis allowed).