Interaction¶
cyhole.jupiter.Jupiter
¶
Jupiter(
tier: JupiterApiTier = JupiterApiTier.LITE,
api_key: str | None = None,
headers: Any | None = None,
)
Bases: Interaction
flowchart TD
cyhole.jupiter.Jupiter[Jupiter]
cyhole.core.interaction.Interaction[Interaction]
cyhole.core.interaction.Interaction --> cyhole.jupiter.Jupiter
click cyhole.jupiter.Jupiter href "" "cyhole.jupiter.Jupiter"
click cyhole.core.interaction.Interaction href "" "cyhole.core.interaction.Interaction"
Class used to connect Jupiter API, one of them most popular Solana DEX.
To have access Jupiter API is not required an API key if you are using the lite API tier.
If using the pro or ultra API tiers, an API key is required.
Check supported API tiers at: https://dev.jup.ag/portal/rate-limit
Check https://dev.jup.ag/api-reference for all the details on the available endpoints.
Example
import asyncio
from cyhole.jupiter import Jupiter
from cyhole.core.token.solana import JUP
jupiter = Jupiter()
# Get current price of JUP on Solana
# synchronous
response = jupiter.client.get_price([JUP.address])
print("Current JUP/USDC:", response.data[JUP.address].price)
# asynchronous
async def main() -> None:
async with jupiter.async_client as client:
response = await client.get_price([JUP.address])
print("Current JUP/USDC:", response.data[JUP.address].price)
asyncio.run(main())
Source code in src/cyhole/jupiter/interaction.py
93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 | |
_get_price
¶
_get_price(
sync: Literal[True], address: list[str]
) -> GetPriceResponse
_get_price(
sync: Literal[False], address: list[str]
) -> Coroutine[None, None, GetPriceResponse]
_get_price(
sync: bool, address: list[str]
) -> (
GetPriceResponse
| Coroutine[None, None, GetPriceResponse]
)
This function refers to the GET Price API endpoint, and it is used to get the current USD price for up to 50 tokens on Solana from Jupiter.
Returns None for a token when price data is unavailable or unreliable
(e.g. no trades in the last 7 days, or flagged as suspicious).
Parameters:
| Name | Type | Description | Default |
|---|---|---|---|
address
|
list[str]
|
list of token mint addresses to query. Maximum 50 per request.
For example, |
required |
Returns:
| Type | Description |
|---|---|
GetPriceResponse | Coroutine[None, None, GetPriceResponse]
|
mapping of token mint address to price data. |
Source code in src/cyhole/jupiter/interaction.py
180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 | |
_get_swap_order
¶
_get_swap_order(
sync: Literal[True], params: GetSwapOrderParams
) -> GetSwapOrderResponse
_get_swap_order(
sync: Literal[False], params: GetSwapOrderParams
) -> Coroutine[None, None, GetSwapOrderResponse]
_get_swap_order(
sync: bool, params: GetSwapOrderParams
) -> (
GetSwapOrderResponse
| Coroutine[None, None, GetSwapOrderResponse]
)
This function refers to the GET Swap - Order API endpoint, and it is used to get a swap quote and a fully assembled transaction using Jupiter Swap v2 API.
The Meta-Aggregator path competes across all routing engines (Metis, JupiterZ RFQ, DFlow, OKX)
to return the best price. When taker is provided the response includes a ready-to-sign
base64-encoded transaction; combine with post_swap_execute to land it on-chain.
Parameters:
| Name | Type | Description | Default |
|---|---|---|---|
params
|
GetSwapOrderParams
|
input params describing the swap. See |
required |
Returns:
| Type | Description |
|---|---|
GetSwapOrderResponse | Coroutine[None, None, GetSwapOrderResponse]
|
Quote and assembled transaction from Jupiter Swap v2 API. |
Source code in src/cyhole/jupiter/interaction.py
217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 | |
_post_swap_execute
¶
_post_swap_execute(
sync: Literal[True], body: PostSwapExecuteBody
) -> PostSwapExecuteResponse
_post_swap_execute(
sync: Literal[False], body: PostSwapExecuteBody
) -> Coroutine[None, None, PostSwapExecuteResponse]
_post_swap_execute(
sync: bool, body: PostSwapExecuteBody
) -> (
PostSwapExecuteResponse
| Coroutine[None, None, PostSwapExecuteResponse]
)
This function refers to the POST Swap - Execute API endpoint,
and it is used to execute a signed swap transaction created by get_swap_order.
First call get_swap_order with a valid taker to obtain the base64 transaction and the
request_id. Sign the transaction with the taker's wallet, then submit both via this endpoint.
Parameters:
| Name | Type | Description | Default |
|---|---|---|---|
body
|
PostSwapExecuteBody
|
signed transaction and request ID from |
required |
Returns:
| Type | Description |
|---|---|
PostSwapExecuteResponse | Coroutine[None, None, PostSwapExecuteResponse]
|
Execution result including status, signature, and amount details. |
Source code in src/cyhole/jupiter/interaction.py
243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 | |
_get_swap_build
¶
_get_swap_build(
sync: Literal[True], params: GetSwapBuildParams
) -> GetSwapBuildResponse
_get_swap_build(
sync: Literal[False], params: GetSwapBuildParams
) -> Coroutine[None, None, GetSwapBuildResponse]
_get_swap_build(
sync: bool, params: GetSwapBuildParams
) -> (
GetSwapBuildResponse
| Coroutine[None, None, GetSwapBuildResponse]
)
This function refers to the GET Swap - Build API endpoint, and it is used to get raw swap instructions for custom transaction building using Jupiter Swap v2 Router path.
Unlike get_swap_order, this endpoint returns individual Solana instructions rather than an assembled
transaction, allowing integrators to compose their own transaction. Routing is handled exclusively
by the Metis on-chain router (no RFQ market makers). Combine with post_swap_submit to land the
transaction via Jupiter's infrastructure.
Parameters:
| Name | Type | Description | Default |
|---|---|---|---|
params
|
GetSwapBuildParams
|
input params describing the swap. See |
required |
Returns:
| Type | Description |
|---|---|
GetSwapBuildResponse | Coroutine[None, None, GetSwapBuildResponse]
|
Raw instructions and route plan for custom transaction assembly. |
Source code in src/cyhole/jupiter/interaction.py
269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 | |
_post_swap_submit
¶
_post_swap_submit(
sync: Literal[True], body: PostSwapSubmitBody
) -> PostSwapSubmitResponse
_post_swap_submit(
sync: Literal[False], body: PostSwapSubmitBody
) -> Coroutine[None, None, PostSwapSubmitResponse]
_post_swap_submit(
sync: bool, body: PostSwapSubmitBody
) -> (
PostSwapSubmitResponse
| Coroutine[None, None, PostSwapSubmitResponse]
)
This function refers to the POST Swap - Submit API endpoint, and it is used to submit any signed Solana transaction through Jupiter's proprietary landing pipeline.
The transaction must include a SOL tip (minimum 0.001 SOL / 1,000,000 lamports) to incentivise validators. This endpoint is zero-credit-cost and available on all plans including keyless access.
Parameters:
| Name | Type | Description | Default |
|---|---|---|---|
body
|
PostSwapSubmitBody
|
base64-encoded signed Solana transaction.
See |
required |
Returns:
| Type | Description |
|---|---|
PostSwapSubmitResponse | Coroutine[None, None, PostSwapSubmitResponse]
|
Transaction signature after successful submission. |
Source code in src/cyhole/jupiter/interaction.py
296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 | |
_get_token_search
¶
_get_token_search(
sync: Literal[True], address: str | list[str]
) -> GetTokenSearchResponse
_get_token_search(
sync: Literal[False], address: str | list[str]
) -> Coroutine[None, None, GetTokenSearchResponse]
_get_token_search(
sync: bool, address: str | list[str]
) -> (
GetTokenSearchResponse
| Coroutine[None, None, GetTokenSearchResponse]
)
This function refers to the GET Token Search API endpoint, with a specific focus on retrieving the information of a list of token given its addresses, names or symbols.
Parameters:
| Name | Type | Description | Default |
|---|---|---|---|
address
|
str | list[str]
|
list of addresses, names or symbols of the tokens to check.
For example, |
required |
Returns:
| Type | Description |
|---|---|
GetTokenSearchResponse | Coroutine[None, None, GetTokenSearchResponse]
|
Information of the tokens. |
Source code in src/cyhole/jupiter/interaction.py
322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 | |
_get_token_tag
¶
_get_token_tag(
sync: Literal[True], tag: str | JupiterTokenTagType
) -> GetTokenTagResponse
_get_token_tag(
sync: Literal[False], tag: str | JupiterTokenTagType
) -> Coroutine[None, None, GetTokenTagResponse]
_get_token_tag(
sync: bool, tag: str | JupiterTokenTagType
) -> (
GetTokenTagResponse
| Coroutine[None, None, GetTokenTagResponse]
)
This function refers to the GET Token Tag API endpoint,
and it is used to retrieved the list of tokens eligible for trading, managed by Jupiter.
Choose the tokens list according to tag field.
Parameters:
| Name | Type | Description | Default |
|---|---|---|---|
tag
|
str | JupiterTokenTagType
|
Jupiter manages the tradable tokens through a set of tags in order to guarantee its
core values and provide a secure service. The supported tages are available on |
required |
Returns:
| Type | Description |
|---|---|
GetTokenTagResponse | Coroutine[None, None, GetTokenTagResponse]
|
List of Jupiter's tokens list. |
Source code in src/cyhole/jupiter/interaction.py
364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 | |
_get_token_category
¶
_get_token_category(
sync: Literal[True],
category: str | JupiterTokenCategory,
interval: str | JupiterTokenInterval,
) -> GetTokenCategoryResponse
_get_token_category(
sync: Literal[False],
category: str | JupiterTokenCategory,
interval: str | JupiterTokenInterval,
) -> Coroutine[None, None, GetTokenCategoryResponse]
_get_token_category(
sync: bool,
category: str | JupiterTokenCategory,
interval: str | JupiterTokenInterval,
) -> (
GetTokenCategoryResponse
| Coroutine[None, None, GetTokenCategoryResponse]
)
This function refers to the GET Token Category API endpoint, and it is used to retrieved the list of token according to a category in a specific interval.
Parameters:
| Name | Type | Description | Default |
|---|---|---|---|
category
|
str | JupiterTokenCategory
|
category to filter by. |
required |
interval
|
str | JupiterTokenInterval
|
time range to consider to extract. |
required |
Returns:
| Type | Description |
|---|---|
GetTokenCategoryResponse | Coroutine[None, None, GetTokenCategoryResponse]
|
List of Jupiter's tokens list. |
Source code in src/cyhole/jupiter/interaction.py
403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426 427 428 429 430 431 432 433 | |
_get_token_recent
¶
_get_token_recent(
sync: Literal[True], limit: int | None = None
) -> GetTokenRecentResponse
_get_token_recent(
sync: Literal[False], limit: int | None = None
) -> Coroutine[None, None, GetTokenRecentResponse]
_get_token_recent(
sync: bool, limit: int | None = None
) -> (
GetTokenRecentResponse
| Coroutine[None, None, GetTokenRecentResponse]
)
This function refers to the GET Token Recent API endpoint, and it is used to retrieve the list of recently created tokens with their first pool information.
Parameters:
| Name | Type | Description | Default |
|---|---|---|---|
limit
|
int | None
|
maximum number of tokens to return. API defaults to |
None
|
Returns:
| Type | Description |
|---|---|
GetTokenRecentResponse | Coroutine[None, None, GetTokenRecentResponse]
|
List of Jupiter's recently created tokens. |
Source code in src/cyhole/jupiter/interaction.py
441 442 443 444 445 446 447 448 449 450 451 452 453 454 455 456 457 458 459 460 461 462 463 464 465 466 | |
_get_token_verify_check_eligibility
¶
_get_token_verify_check_eligibility(
sync: Literal[True], token_id: str
) -> GetTokenVerifyCheckEligibilityResponse
_get_token_verify_check_eligibility(
sync: Literal[False], token_id: str
) -> Coroutine[
None, None, GetTokenVerifyCheckEligibilityResponse
]
_get_token_verify_check_eligibility(
sync: bool, token_id: str
) -> (
GetTokenVerifyCheckEligibilityResponse
| Coroutine[
None, None, GetTokenVerifyCheckEligibilityResponse
]
)
This function refers to the GET Token Verify - Check Eligibility API endpoint, and it is used to determine whether a token is eligible for express verification on Jupiter.
Parameters:
| Name | Type | Description | Default |
|---|---|---|---|
token_id
|
str
|
mint address of the token to check. |
required |
Returns:
| Type | Description |
|---|---|
GetTokenVerifyCheckEligibilityResponse | Coroutine[None, None, GetTokenVerifyCheckEligibilityResponse]
|
Eligibility status indicating whether verification and metadata updates are permitted. |
Raises:
| Type | Description |
|---|---|
JupiterException
|
if the API returns an error. |
Source code in src/cyhole/jupiter/interaction.py
474 475 476 477 478 479 480 481 482 483 484 485 486 487 488 489 490 | |
_get_token_verify_craft_txn
¶
_get_token_verify_craft_txn(
sync: Literal[True], sender_address: str
) -> GetTokenVerifyCraftTxnResponse
_get_token_verify_craft_txn(
sync: Literal[False], sender_address: str
) -> Coroutine[None, None, GetTokenVerifyCraftTxnResponse]
_get_token_verify_craft_txn(
sync: bool, sender_address: str
) -> (
GetTokenVerifyCraftTxnResponse
| Coroutine[None, None, GetTokenVerifyCraftTxnResponse]
)
This function refers to the GET Token Verify - Craft Transaction API endpoint, and it is used to obtain an unsigned transaction for the 1000 JUP express verification payment.
Parameters:
| Name | Type | Description | Default |
|---|---|---|---|
sender_address
|
str
|
wallet address that will sign and submit the payment transaction. |
required |
Returns:
| Type | Description |
|---|---|
GetTokenVerifyCraftTxnResponse | Coroutine[None, None, GetTokenVerifyCraftTxnResponse]
|
Unsigned transaction details including the base64-encoded transaction and a |
GetTokenVerifyCraftTxnResponse | Coroutine[None, None, GetTokenVerifyCraftTxnResponse]
|
required by the execute step. |
Raises:
| Type | Description |
|---|---|
JupiterException
|
if the API returns an error. |
Source code in src/cyhole/jupiter/interaction.py
498 499 500 501 502 503 504 505 506 507 508 509 510 511 512 513 514 515 | |
_post_token_verify_execute
¶
_post_token_verify_execute(
sync: Literal[True], body: PostTokenVerifyExecuteBody
) -> PostTokenVerifyExecuteResponse
_post_token_verify_execute(
sync: Literal[False], body: PostTokenVerifyExecuteBody
) -> Coroutine[None, None, PostTokenVerifyExecuteResponse]
_post_token_verify_execute(
sync: bool, body: PostTokenVerifyExecuteBody
) -> (
PostTokenVerifyExecuteResponse
| Coroutine[None, None, PostTokenVerifyExecuteResponse]
)
This function refers to the POST Token Verify - Execute API endpoint, and it is used to submit a signed verification transaction and project details to complete the express verification flow.
Parameters:
| Name | Type | Description | Default |
|---|---|---|---|
body
|
PostTokenVerifyExecuteBody
|
the body containing the signed transaction, request ID, sender address, token mint, Twitter handle, description, and optional token metadata. |
required |
Returns:
| Type | Description |
|---|---|
PostTokenVerifyExecuteResponse | Coroutine[None, None, PostTokenVerifyExecuteResponse]
|
Verification execution result including submission status and on-chain transaction signature. |
Raises:
| Type | Description |
|---|---|
JupiterException
|
if the API returns an error. |
Source code in src/cyhole/jupiter/interaction.py
523 524 525 526 527 528 529 530 531 532 533 534 535 536 537 538 539 540 541 542 543 544 545 546 547 548 549 550 551 552 553 554 555 556 557 558 559 560 561 562 563 564 | |
_post_recurring_create_order
¶
_post_recurring_create_order(
sync: Literal[True], body: PostRecurringCreateOrderBody
) -> PostRecurringCreateOrderResponse
_post_recurring_create_order(
sync: Literal[False], body: PostRecurringCreateOrderBody
) -> Coroutine[
None, None, PostRecurringCreateOrderResponse
]
_post_recurring_create_order(
sync: bool, body: PostRecurringCreateOrderBody
) -> (
PostRecurringCreateOrderResponse
| Coroutine[
None, None, PostRecurringCreateOrderResponse
]
)
This function refers to the POST Recurring - Create Order API endpoint, and it is used to receive an unsigned transaction to perform the creation of an order via Jupiter API.
The creation order could be of two kinds
- time-based: these orders are designed to create a set of recurring orders starting from a initial amount. This amount is divided equally in the number of orders to create, and each order is created with a time interval between them. The time interval is specified at the creation of the order.
- price-based: these orders are designed to create a set of recurring orders starting
from a initial input token amount. This amount is then used to place orders (over a decided
time interval) act to increase the portafolio value by a fixed
USDamount every time. For example, if we put an initial 1SOLamount and we want to buyBONKover time for 50USDevery 1 hour, then the order will proceed to place an order to buy every 1 hour for 50USDofBONKusing the current price ofSOLtoBONK. Important: price-based orders are opened indefinitely until the user closes them.
Parameters:
| Name | Type | Description | Default |
|---|---|---|---|
body
|
PostRecurringCreateOrderBody
|
the body to sent to Jupiter API that describe the order. More details in the object definition. |
required |
Returns:
| Type | Description |
|---|---|
PostRecurringCreateOrderResponse | Coroutine[None, None, PostRecurringCreateOrderResponse]
|
Unsigned transaction created by Jupiter API. |
Source code in src/cyhole/jupiter/interaction.py
572 573 574 575 576 577 578 579 580 581 582 583 584 585 586 587 588 589 590 591 592 593 594 595 596 597 598 599 600 601 602 603 604 605 606 607 608 609 610 611 612 613 614 615 616 617 618 619 620 621 622 623 624 625 626 627 628 | |
_get_recurring_orders
¶
_get_recurring_orders(
sync: Literal[True],
user_public_key: str,
status: JupiterOrderStatus,
recurring_type: JupiterRecurringType,
include_failed: bool = False,
page: int = 1,
input_mint: str | None = None,
output_mint: str | None = None,
) -> GetRecurringOrdersResponse
_get_recurring_orders(
sync: Literal[False],
user_public_key: str,
status: JupiterOrderStatus,
recurring_type: JupiterRecurringType,
include_failed: bool = False,
page: int = 1,
input_mint: str | None = None,
output_mint: str | None = None,
) -> Coroutine[None, None, GetRecurringOrdersResponse]
_get_recurring_orders(
sync: bool,
user_public_key: str,
status: JupiterOrderStatus,
recurring_type: JupiterRecurringType,
include_failed: bool = False,
page: int = 1,
input_mint: str | None = None,
output_mint: str | None = None,
) -> (
GetRecurringOrdersResponse
| Coroutine[None, None, GetRecurringOrdersResponse]
)
This function refers to the GET Recurring - Orders API endpoint, and it is used to retrieve the list of recurring orders associated to a wallet via Jupiter API.
Parameters:
| Name | Type | Description | Default |
|---|---|---|---|
user_public_key
|
str
|
Public Key of the Owner wallet. |
required |
status
|
JupiterOrderStatus
|
status of the orders to retrieve. |
required |
recurring_type
|
JupiterRecurringType
|
type of the recurring order to retrieve. |
required |
include_failed
|
bool
|
flag to include failed orders. |
False
|
page
|
int
|
specify which 'page' of orders to return. |
1
|
input_mint
|
str | None
|
filter orders by input token mint address. |
None
|
output_mint
|
str | None
|
filter orders by output token mint address. |
None
|
Returns:
| Type | Description |
|---|---|
GetRecurringOrdersResponse | Coroutine[None, None, GetRecurringOrdersResponse]
|
List of orders associated to the input wallet. |
Source code in src/cyhole/jupiter/interaction.py
656 657 658 659 660 661 662 663 664 665 666 667 668 669 670 671 672 673 674 675 676 677 678 679 680 681 682 683 684 685 686 687 688 689 690 691 692 693 694 695 696 697 698 699 700 701 702 703 704 705 706 707 708 709 710 711 | |
_post_recurring_cancel_order
¶
_post_recurring_cancel_order(
sync: Literal[True],
order_id: str,
user_public_key: str,
recurring_type: JupiterRecurringType,
) -> PostRecurringCancelOrderResponse
_post_recurring_cancel_order(
sync: Literal[False],
order_id: str,
user_public_key: str,
recurring_type: JupiterRecurringType,
) -> Coroutine[
None, None, PostRecurringCancelOrderResponse
]
_post_recurring_cancel_order(
sync: bool,
order_id: str,
user_public_key: str,
recurring_type: JupiterRecurringType,
) -> (
PostRecurringCancelOrderResponse
| Coroutine[
None, None, PostRecurringCancelOrderResponse
]
)
This function refers to the POST Recurring - Cancel Order API endpoint, and it is used to cancel an order placed using the Jupiter Recurring API.
Parameters:
| Name | Type | Description | Default |
|---|---|---|---|
order_id
|
str
|
ID of the recurring order. |
required |
user_public_key
|
str
|
Public Key of the Owner wallet. |
required |
recurring_type
|
JupiterRecurringType
|
type of the recurring order to retrieve. |
required |
Returns:
| Type | Description |
|---|---|
PostRecurringCancelOrderResponse | Coroutine[None, None, PostRecurringCancelOrderResponse]
|
Cancel information provided by Jupiter API. |
Source code in src/cyhole/jupiter/interaction.py
719 720 721 722 723 724 725 726 727 728 729 730 731 732 733 734 735 736 737 738 739 740 741 742 743 744 745 746 747 748 749 750 751 752 753 754 755 756 757 | |
_post_recurring_execute
¶
_post_recurring_execute(
sync: Literal[True],
signed_transaction_id: str,
request_id: str,
) -> PostRecurringExecuteResponse
_post_recurring_execute(
sync: Literal[False],
signed_transaction_id: str,
request_id: str,
) -> Coroutine[None, None, PostRecurringExecuteResponse]
_post_recurring_execute(
sync: bool, signed_transaction_id: str, request_id: str
) -> (
PostRecurringExecuteResponse
| Coroutine[None, None, PostRecurringExecuteResponse]
)
This function refers to the POST Recurring - Execute API endpoint,
and it is used to execute an "action" order using the different endpoints of the Jupiter Recurring API. For example,
creating a new recurring order (post_recurring_create_order) or canceling an existing one (post_recurring_cancel_order).
First, it is required to call the endpoint of the desired action (create, cancel, deposit, withdraw). From the response,
is then possible to get the Request ID (PostRecurring*Response.request_id) and the transaction ID (PostRecurring*Response.transaction_id).
The transaction ID must be then signed by the payer walled to get the signed_transaction_id that can be finally used
to execute the action.
Parameters:
| Name | Type | Description | Default |
|---|---|---|---|
signed_transaction_id
|
str
|
the transaction ID coming from the Recurring API responses signed by the payer wallet. |
required |
request_id
|
str
|
the same request ID coming from the responses. |
required |
Returns:
| Type | Description |
|---|---|
PostRecurringExecuteResponse | Coroutine[None, None, PostRecurringExecuteResponse]
|
Order execution information provided by Jupiter API. |
Source code in src/cyhole/jupiter/interaction.py
765 766 767 768 769 770 771 772 773 774 775 776 777 778 779 780 781 782 783 784 785 786 787 788 789 790 791 792 793 794 795 796 797 798 799 800 801 802 803 804 805 806 807 | |
_raise
¶
_raise(exception: HTTPError) -> JupiterException
Internal function used to raise the correct Jupiter exception according to the error code provided by the API.
Parameters:
| Name | Type | Description | Default |
|---|---|---|---|
exception
|
HTTPError
|
the HTTP error returned from Jupiter API. |
required |
Raises:
| Type | Description |
|---|---|
JupiterNoRouteFoundError
|
for error code |
JupiterInvalidRequest
|
for error code |
JupiterException
|
general exception raised when an unknown error code is found or a different error is found. |
Source code in src/cyhole/jupiter/interaction.py
809 810 811 812 813 814 815 816 817 818 819 820 821 822 823 824 825 826 827 828 829 830 831 832 833 834 835 836 837 | |