Jupiter Trigger icon

Jupiter Trigger

Jupiter Trigger API operations

Actions5

Overview

The "Jupiter Trigger" node interacts with the Jupiter Trigger API to manage trigger orders related to token swaps or trades. It supports creating new trigger orders, canceling single or multiple orders, executing signed transactions, and retrieving active or historical trigger orders.

This node is beneficial in scenarios where automated trading or conditional token swaps are required on the Solana blockchain or similar environments. For example, a user can create an order that triggers a token swap when the price reaches a certain threshold, or cancel existing orders programmatically.

Practical examples:

  • Creating a trigger order to swap tokens when the market price goes above or below a specified value.
  • Canceling one or more pending trigger orders for a specific wallet.
  • Executing a pre-signed transaction returned from the API.
  • Fetching all active or historical trigger orders for a given account.

Properties

Name Meaning
Base URL Base URL for Jupiter Trigger API (default: https://lite-api.jup.ag/trigger/v1)
Operation The action to perform: Create Order, Cancel Order, Cancel Orders, Execute, Get Trigger Orders
Input Mint Input token mint address (required for Create Order)
Output Mint Output token mint address (required for Create Order)
Amount Amount in smallest unit (lamports/atoms) to trade (required for Create Order)
Maker Maker wallet address (required for Create Order, Cancel Order, Cancel Orders)
Trigger Price Price at which to trigger the order (required for Create Order)
Trigger Condition Condition for triggering the order: "Above" or "Below" (default: "Above")
Slippage BPS Slippage in basis points (default: 50)
Signed Transaction Base64 encoded signed transaction (required for Execute operation)
Request ID Request ID from createOrder or cancelOrder response (required for Execute operation)
Account Account address to get orders for (required for Get Trigger Orders)
Order Type Type of orders to retrieve: "Active" or "Historical" (default: "Active")
Order ID Specific order ID to cancel (optional for Cancel Order)
Order IDs Comma-separated list of order IDs to cancel (optional for Cancel Orders)

Output

The node outputs JSON data corresponding to the response from the Jupiter Trigger API for each operation:

  • Create Order: Returns details of the newly created trigger order.
  • Cancel Order(s): Returns confirmation of canceled order(s).
  • Execute: Returns the result of executing the signed transaction.
  • Get Trigger Orders: Returns a list of active or historical trigger orders for the specified account.

The output JSON structure depends on the API response but generally includes order identifiers, status, and relevant metadata.

No binary data output is produced by this node.

Dependencies

  • Requires access to the Jupiter Trigger API endpoint (default base URL provided).
  • Optionally uses an API key credential for authentication via the HTTP header x-api-key.
  • No other external dependencies or environment variables are required.

Troubleshooting

  • Common issues:

    • Incorrect or missing required parameters (e.g., maker address, token mints) will cause API errors.
    • Invalid or expired API keys may lead to authentication failures.
    • Network connectivity issues to the API endpoint can cause request timeouts or failures.
    • Providing malformed signed transactions during execution will result in errors.

  • Error messages:

    • "Unknown operation": Occurs if an unsupported operation is selected; ensure the operation name matches supported options.
    • API error responses are passed through as JSON; check the message for details such as invalid parameters or authorization failures.
    • If the node is set to continue on fail, errors will be included in the output JSON under an error field.

  • Resolution tips:

    • Verify all required fields are correctly filled.
    • Confirm API key validity and permissions.
    • Check network access to the configured Base URL.
    • Validate signed transactions before execution.

Links and References

Discussion