Jupiter Trigger icon

Jupiter Trigger

Jupiter Trigger API operations

Actions5

Overview

This node interacts with the Jupiter Trigger API to manage trigger orders related to cryptocurrency trading. It supports operations such as creating new trigger orders, canceling single or multiple orders, executing signed transactions, and retrieving active or historical trigger orders for a specified account.

Common scenarios where this node is beneficial include:

  • Automating order management on the Jupiter platform by programmatically creating or canceling trigger orders.
  • Monitoring active or past orders for an account to analyze trading activity.
  • Executing pre-signed transactions securely through the API.

For example, a user can retrieve all active trigger orders for their account to monitor pending trades or create a new trigger order that executes when a token price crosses a specified threshold.

Properties

Name Meaning
Base URL Base URL for Jupiter Trigger API (default: https://lite-api.jup.ag/trigger/v1)
Account Account address to get orders for
Order Type Type of orders to retrieve; options: Active (currently open orders), Historical (past orders)

Output

The node outputs JSON data representing the response from the Jupiter Trigger API for the requested operation. For the "Get Trigger Orders" operation, the output JSON contains the list of trigger orders associated with the specified account and order type (active or historical).

The output structure depends on the API response but generally includes details about each trigger order such as order ID, maker address, input/output tokens, amount, trigger price, condition, and status.

No binary data output is produced by this node.

Dependencies

  • Requires access to the Jupiter Trigger API endpoint, configurable via the Base URL property.
  • Optionally uses an API key credential for authentication if provided; the key is sent in the x-api-key HTTP header.
  • No additional external dependencies beyond standard HTTP requests.

Troubleshooting

  • Common issues:

    • Invalid or missing account address may result in empty or error responses.
    • Incorrect Base URL or network connectivity problems will cause request failures.
    • Missing or invalid API key (if required by the API) can lead to authorization errors.

  • Error messages:

    • "Unknown operation": Indicates an unsupported operation was selected; ensure the operation name matches one of the supported options.
    • HTTP errors returned by the API (e.g., 401 Unauthorized, 404 Not Found) should be checked against API documentation and credentials.

  • Resolution tips:

    • Verify the account address format and correctness.
    • Confirm the Base URL is reachable and correct.
    • Provide a valid API key credential if the API requires authentication.
    • Use the node's "Continue On Fail" option to handle errors gracefully during batch processing.

Links and References

Discussion