Jupiter Ultra icon

Jupiter Ultra

Jupiter Ultra API operations
Join our community

Actions6

Overview

This node integrates with the Jupiter Ultra API, a service primarily used for token swaps and related operations on Solana blockchain. It supports multiple operations such as fetching token balances, creating swap orders, executing signed transactions, retrieving liquidity routers, searching tokens, and getting token risk warnings.

The Execute operation specifically submits a base64-encoded signed transaction to the Jupiter Ultra API for processing. This is useful when you have already created and signed a transaction (e.g., a token swap) and want to broadcast it via Jupiter's infrastructure.

Practical examples:

  • After obtaining a swap quote and unsigned transaction from the "Order" operation, you sign the transaction externally (e.g., in a wallet or signing service), then use this node’s Execute operation to submit that signed transaction.
  • Automating token swaps by programmatically submitting signed transactions without manual intervention.

Properties

Name Meaning
Base URL The base URL of the Jupiter Ultra API endpoint. Defaults to https://lite-api.jup.ag/ultra/v1.
Signed Transaction Base64 encoded signed transaction string to be submitted for execution. Required.
Request ID Request ID obtained from the order endpoint corresponding to the transaction. Required.

Output

The node outputs the JSON response returned by the Jupiter Ultra API after submitting the signed transaction. This typically includes details about the transaction status, confirmation, or any errors returned by the API.

The output structure is:

{
  "json": {
    // Response fields from Jupiter Ultra API execute endpoint
  },
  "pairedItem": <index_of_input_item>
}

No binary data output is produced by this operation.

Dependencies

  • Requires access to the Jupiter Ultra API endpoint.
  • Optionally uses an API key credential if configured; the key is sent in the x-api-key HTTP header.
  • No other external dependencies are required.
  • Network connectivity to the specified Base URL must be available.

Troubleshooting

  • Common issues:

    • Invalid or malformed signed transaction string will cause the API to reject the request.
    • Incorrect or missing Request ID may result in errors or failed execution.
    • Network or authentication failures if the API key is invalid or missing when required.

  • Error messages:

    • Errors from the API will be returned in the node output under an error message field.
    • If the node encounters an unknown operation or missing parameters, it throws an error indicating the problem.

  • Resolution tips:

    • Ensure the signed transaction is correctly base64 encoded and corresponds to the provided Request ID.
    • Verify API key credentials if authentication errors occur.
    • Check network connectivity and correct Base URL configuration.

Links and References

Discussion