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 deposit and withdrawal transactions.

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 purchase of a token every week or create deposits that trigger when a token reaches a certain price.

Practical examples:

  • Automatically buying a fixed amount of a token every month.
  • Canceling an existing recurring order if market conditions change.
  • Depositing funds into a price-triggered order when the token price hits a target.
  • Retrieving all active recurring orders for monitoring purposes.

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: Create Order, Cancel Order, Execute, Get Recurring Orders, Price Deposit, Price Withdraw.
Recurring Type Type of recurring order: Time or Price.
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 (used in Get Recurring Orders operation).
Order Type Type of orders to retrieve: Active or Historical (used in Get Recurring Orders operation).
Input Mint Input token mint address (required for createOrder, cancelOrder, priceDeposit, priceWithdraw).
Output Mint Output token mint address (required for createOrder, cancelOrder, priceDeposit, priceWithdraw).
Amount Amount in smallest unit (lamports/atoms) (required for createOrder, priceDeposit, priceWithdraw).
Maker Maker wallet address (required for createOrder, cancelOrder, priceDeposit, priceWithdraw).
Order ID Order ID (optional for cancelOrder operation).
Slippage BPS Slippage in basis points (default: 50) (used in createOrder operation).

Output

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

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.
  • Network connectivity to the API endpoint is required.

Troubleshooting

  • Common issues:

    • Missing or incorrect input parameters such as token mint addresses or maker wallet address may cause API errors.
    • Invalid or expired API keys will result in authentication failures.
    • Network connectivity problems can prevent successful API calls.
    • Using an unsupported operation value will throw an error.

  • Error messages:

    • "Unknown operation: <operation>": Indicates an invalid operation was selected; verify the operation name.
    • API errors returned from the Jupiter Recurring service will be included in the node's output JSON under an error message.

  • Resolutions:

    • Double-check all required fields are provided and correctly formatted.
    • Ensure the API key credential is properly set up and valid.
    • Verify network access to the API endpoint.
    • Use the correct operation names as listed in the properties.

Links and References

Discussion