Jupiter Recurring icon

Jupiter Recurring

Jupiter Recurring API operations

Actions6

Overview

The "Jupiter Recurring" node integrates with the Jupiter Recurring API to manage recurring token orders on a blockchain platform. It supports operations such as creating and canceling recurring orders, executing signed transactions, retrieving active or historical orders, and handling price-based deposits and withdrawals.

This node is beneficial for users who want to automate recurring token trades or transfers based on time intervals or price triggers. For example, a user can set up a recurring order to buy a specific token every week or withdraw tokens when a certain price condition is met.

Practical examples:

  • Automatically create a recurring purchase order of a token every month.
  • Cancel an existing recurring order if market conditions change.
  • Execute a signed transaction received from an external wallet.
  • Retrieve all active recurring orders for a given account.
  • Create deposit or withdrawal transactions triggered by price changes.

Properties

Name Meaning
Base URL The base URL for the Jupiter Recurring API (default: https://lite-api.jup.ag/recurring/v1).
Operation The action to perform. Options: Cancel Order, Create Order, Execute, Get Recurring Orders, Price Deposit, Price Withdraw.
Recurring Type Type of recurring order. Options: Time, Price. Used in create, cancel, and execute operations.
Signed Transaction Base64 encoded signed transaction string. Required for the Execute operation.
Request ID Request ID obtained from create or cancel order responses. Required for the Execute operation.
Account Wallet/account address to retrieve recurring orders for. Used in Get Recurring Orders.
Order Type Type of orders to retrieve. Options: Active, Historical. Used in Get Recurring Orders.
Input Mint Input token mint address (blockchain token identifier). Required for create, cancel, price deposit, and price withdraw operations.
Output Mint Output token mint address. Required for create, cancel, price deposit, and price withdraw operations.
Amount Amount in smallest unit (e.g., lamports or atoms) to deposit or withdraw. Required for create, price deposit, and price withdraw operations.
Maker Maker wallet address involved in the order. Required for create, cancel, price deposit, and price withdraw operations.
Order ID Optional order ID for cancel operations.
Slippage BPS Slippage tolerance in basis points (default 50). Used only in create order operation.

Output

The node outputs JSON data corresponding to the response from the Jupiter Recurring API for each operation. The structure varies depending on the operation but generally includes details about the created or canceled orders, executed transactions, or lists of recurring orders.

If the operation involves creating deposit or withdrawal transactions, the output contains the transaction data necessary to proceed with those actions.

No binary data output is produced by this node.

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:

    • Missing or incorrect input parameters such as token mint addresses or maker wallet address will cause API errors.
    • Invalid or expired API keys may result in authentication failures.
    • Network connectivity issues to the Base URL will cause request failures.
    • Using an unsupported operation value will throw an error.

  • Error messages:

    • "Unknown operation: <operation>": Indicates an invalid operation parameter; verify the selected operation.
    • API error responses will be returned in the node output if "Continue On Fail" is enabled.
    • Authentication errors typically indicate missing or invalid API key credentials.

  • Resolutions:

    • Double-check all required input fields for correctness.
    • Ensure the API key credential is properly set up in n8n.
    • Verify network access to the Jupiter Recurring API endpoint.
    • Use the correct operation names as listed in the properties.

Links and References

Discussion