Jupiter Recurring icon

Jupiter Recurring

Jupiter Recurring API operations

Actions6

Overview

This node integrates with the Jupiter Recurring API to manage recurring orders related to token swaps or transactions. It supports operations such as creating, canceling, executing signed transactions, retrieving active or historical recurring orders, and managing price-based deposits and withdrawals.

A common use case is automating periodic token swaps or payments on a blockchain platform, where users want to set up recurring transactions without manual intervention. For example, a user could create a recurring order to swap tokens every day or execute a signed transaction triggered by certain conditions.

The "Get Recurring Orders" operation specifically allows users to fetch either active or historical recurring orders for a given account address, enabling monitoring and management of ongoing or past recurring transactions.

Properties

Name Meaning
Base URL The base URL endpoint for the Jupiter Recurring API (default: https://lite-api.jup.ag/recurring/v1).
Account The blockchain account address for which to retrieve recurring orders.
Order Type The type of orders to retrieve: either Active (currently ongoing orders) or Historical (past orders).

Output

The output is a JSON object containing the response from the Jupiter Recurring API for the requested recurring orders. This typically includes details about each recurring order such as identifiers, status, parameters, and timestamps.

The node does not output binary data.

Example structure of the JSON output might include fields like:

{
  "orders": [
    {
      "orderId": "string",
      "status": "active",
      "inputMint": "string",
      "outputMint": "string",
      "amount": "string",
      "maker": "string",
      "recurringType": "time" | "price",
      "createdAt": "timestamp",
      ...
    }
  ]
}

(Note: Exact fields depend on the API response.)

Dependencies

  • Requires access to the Jupiter Recurring API endpoint.
  • Optionally uses an API key credential for authentication if provided; this should be configured in n8n credentials.
  • No other external dependencies are required.

Troubleshooting

  • Common issues:

    • Invalid or missing account address may result in empty or error responses.
    • Network connectivity problems can cause request failures.
    • Using an incorrect base URL will lead to failed API calls.
    • If the API key is required but not provided or invalid, requests may be rejected.

  • Error messages:

    • "Unknown operation": Indicates an unsupported operation was selected; ensure "Get Recurring Orders" is chosen.
    • HTTP errors from the API (e.g., 401 Unauthorized, 404 Not Found) usually indicate credential or endpoint misconfiguration.

  • Resolution tips:

    • Verify the account address format and correctness.
    • Confirm the base URL matches the current Jupiter Recurring API endpoint.
    • Provide a valid API key credential if the API requires authentication.
    • Check network connectivity and firewall settings.

Links and References

Discussion