Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix quoteV6.yaml, autoMultiplier format error #509

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Fix quoteV6.yaml, autoMultiplier format error #509

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions openapi/quoteV6.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -267,7 +267,7 @@ components:
description: The compute unit price to prioritize the transaction, the additional fee will be `computeUnitLimit (1400000) * computeUnitPriceMicroLamports`. If `auto` is used, Jupiter will automatically set a priority fee and it will be capped at 5,000,000 lamports / 0.005 SOL.
type: integer
prioritizationFeeLamports:
description: "Prioritization fee lamports paid for the transaction in addition to the signatures fee. Mutually exclusive with compute_unit_price_micro_lamports. If `auto` is used, Jupiter will automatically set a priority fee and it will be capped at 5,000,000 lamports / 0.005 SOL. If `autoMultiplier` (`{\"autoMultiplier\"}: 3}`) is used, the priority fee will be a multplier on the `auto` fee. If `jitoTipLamports` (`{\"jitoTipLamports\": 5000}`) is used, a tip intruction will be included to Jito and no priority fee will be set. If `priorityLevelWithMaxLamports` (`{\"priorityLevelWithMaxLamports\": {\"priorityLevel\": \"high\", \"maxLamports\": 123423}}`) is used, it will suggest a priority fee based on `medium`, `high`, or `veryHigh` automatically with a cap set by `maxLamports`."
description: "Prioritization fee lamports paid for the transaction in addition to the signatures fee. Mutually exclusive with compute_unit_price_micro_lamports. If `auto` is used, Jupiter will automatically set a priority fee and it will be capped at 5,000,000 lamports / 0.005 SOL. If `autoMultiplier` (`{\"autoMultiplier\": 3}}`) is used, the priority fee will be a multplier on the `auto` fee. If `jitoTipLamports` (`{\"jitoTipLamports\": 5000}`) is used, a tip intruction will be included to Jito and no priority fee will be set. If `priorityLevelWithMaxLamports` (`{\"priorityLevelWithMaxLamports\": {\"priorityLevel\": \"high\", \"maxLamports\": 123423}}`) is used, it will suggest a priority fee based on `medium`, `high`, or `veryHigh` automatically with a cap set by `maxLamports`."
type: integer
asLegacyTransaction:
description: Default is false. Request a legacy transaction rather than the default versioned transaction, needs to be paired with a quote using asLegacyTransaction otherwise the transaction might be too large.
Expand Down Expand Up @@ -488,4 +488,4 @@ components:
description: If `autoSlippage` is set to `true`, our API will use a default `1000` USD value as way to calculate the slippage impact for the smart slippage. You can set a custom USD value using this parameter.
in: query
schema:
type: integer
type: integer