GainiumInstall

Overview

This node integrates with the Gainium API, providing access to various resources such as General data, Bots, Deals, and User information. Specifically, the "Get Supported Exchanges" operation under the "General" resource fetches a list of exchanges supported by Gainium.

Use cases include:

• Retrieving a list of cryptocurrency exchanges supported by Gainium for further trading or analysis.
• Integrating exchange data into workflows that require knowledge of available markets.
• Automating tasks based on supported exchanges without manual lookup.

Example: A user wants to dynamically populate a dropdown in their workflow with all supported exchanges from Gainium to select where to execute trades.

Properties

Note: For this specific operation ("Get Supported Exchanges"), no additional input parameters are required beyond selecting the resource and operation.

Output

The output JSON contains the data returned by the Gainium API endpoint /api/exchanges. It typically includes an array of supported exchanges with their details.

Structure example (simplified):

{
  "data": [
    {
      "exchangeId": "string",
      "name": "string",
      "status": "string",
      "otherDetails": "..."
    },
    ...
  ]
}

• The data field holds the list of supported exchanges.
• Each item represents an exchange with its properties as provided by the API.
• No binary data is output by this operation.

Dependencies

• Requires an API key credential for Gainium API authentication.
• The node uses HMAC SHA-256 signing for request authentication.
• Requires n8n HTTP Request helper to make authenticated calls to Gainium endpoints.
• The Gainium API base URL and credentials must be configured in n8n.

Troubleshooting

• Error: "HMAC generation failed: Web Crypto API not available"
  This indicates the environment does not support the Web Crypto API needed for signing requests. Ensure the runtime environment supports Web Crypto or use a compatible version of Node.js.

• Error: "Error: "
  Returned when the Gainium API responds with an error status. Check the reason message for details, which may indicate invalid credentials, rate limits, or malformed requests.

• Invalid JSON in filterModel (not applicable directly here but relevant for other operations)
  If using JSON input fields, ensure valid JSON syntax to avoid parsing errors.

• No data returned or empty list
  Verify that the Gainium API credentials are correct and have sufficient permissions. Also, check network connectivity.

Links and References

• Gainium Official API Documentation (user should consult for detailed request/response formats)
• n8n Documentation - Creating Custom Nodes
• Web Crypto API - MDN

This summary focuses on the "General" resource and "Get Supported Exchanges" operation as requested.