Jupiter Recurring icon

Jupiter Recurring

Jupiter Recurring API operations

Actions6

Overview

The "Jupiter Recurring" node integrates with the Jupiter Recurring API to manage recurring cryptocurrency orders. It supports operations such as creating new recurring orders, canceling existing ones, executing signed transactions, retrieving active or historical orders, and handling deposits and withdrawals for price-based orders.

This node is beneficial in scenarios where users want to automate periodic trading or investment strategies on the Jupiter platform, such as:

  • Automatically buying or selling tokens at regular time intervals or price points.
  • Managing and canceling recurring orders without manual intervention.
  • Executing pre-signed transactions securely.
  • Tracking active or past recurring orders for portfolio management.
  • Handling deposits and withdrawals related to price-based recurring orders.

For example, a user could set up a recurring order to buy a specific token every week or when its price hits a certain threshold, then later cancel or adjust that order through this node.

Properties

Name Meaning
Base URL The base URL of the Jupiter Recurring API endpoint (default: https://lite-api.jup.ag/recurring/v1).
Recurring Type Type of recurring order; options are: time (based on time intervals) or price (based on price triggers).
Input Mint The mint address of the input token involved in the order.
Output Mint The mint address of the output token involved in the order.
Maker The wallet address of the maker placing or managing the order.
Order ID The identifier of the order to cancel (optional for cancel operations).

These properties are used specifically for the Cancel Order operation.

Output

The node outputs JSON data representing the response from the Jupiter Recurring API for the requested operation. For the Cancel Order operation, the output JSON typically contains confirmation details about the cancellation request, such as status or any relevant metadata returned by the API.

No binary data output is produced by this node.

Example output structure (simplified):

{
  "status": "success",
  "orderId": "1234567890abcdef",
  "message": "Order cancelled successfully"
}

Dependencies

  • Requires access to the Jupiter Recurring API endpoint specified by the Base URL.
  • Optionally uses an API key credential for authentication, which should be configured in n8n credentials and passed via the x-api-key HTTP header.
  • No other external dependencies are required.

Troubleshooting

  • Common Issues:

    • Incorrect or missing API key may result in authentication errors.
    • Invalid or missing required parameters (e.g., maker address, input/output mint addresses) can cause API request failures.
    • Providing an invalid or non-existent Order ID during cancellation might lead to errors or no effect.
    • Network connectivity issues to the Base URL will prevent successful API calls.

  • Error Messages:

    • "Unknown operation": Indicates an unsupported operation was selected; ensure the operation is set to "Cancel Order".
    • API error responses will be included in the node output if "Continue On Fail" is enabled; otherwise, they will stop execution.
    • Validation errors from the API usually specify which parameter is incorrect or missing.

  • Resolution Tips:

    • Verify all required fields are correctly filled.
    • Ensure the API key credential is properly set up and has necessary permissions.
    • Confirm the Base URL is reachable and correct.
    • Use valid mint addresses and wallet addresses in the expected format.

Links and References

Discussion