Fix: Add support for baseToken and quoteToken fields in Jupiter price request #429
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 is my first contribution. I ran into this issue while using the Gateway Jupiter connector from source. These changes resolved the error and allowed the /jupiter/price endpoint to function as expected.
What this does
baseTokenandquoteTokenfields in the /jupiter/price endpointWhy it matters
Without these changes, valid requests using the expected mint address fields fail validation. These changes enable developers to properly integrate Jupiter connector in secure HTTPS mode using token mints.
How to test
/jupiter/pricewith this body:{ "chain": "solana", "network": "mainnet-beta", "connector": "jupiter", "baseToken": "So11111111111111111111111111111111111111112", "quoteToken": "EPjFWdd5AufqSSqeM2qN1xzybapC8G4wEGGkZwyTDt1v", "amount": "1000000", "side": "SELL", "base": true, "quote": false }