Finnhub.io icon

Finnhub.io

Consume Finnhub.io API
Join our community

Actions26

Overview

This node interacts with the Finnhub.io API to retrieve a list of cryptocurrency trading symbols available on a specified exchange. It is useful for workflows that need to dynamically fetch or validate crypto trading pairs before performing further operations, such as price lookups, order placements, or portfolio management.

Example scenarios:

  • Fetching all available trading pairs from Binance to populate a dropdown in a custom workflow.
  • Validating if a specific symbol exists on a given exchange before executing trades.
  • Synchronizing your internal database of supported crypto pairs with those listed on an exchange.

Properties

Name Type Meaning
Exchange String Exchange you want to get the list of symbols from (e.g., "binance").

Output

The output will be a JSON array where each item represents a cryptocurrency trading symbol available on the specified exchange. Each object typically contains fields such as the symbol name and possibly additional metadata provided by Finnhub.io.

Example output:

[
  {
    "symbol": "BTCUSDT",
    "displaySymbol": "BTC/USDT",
    "description": "Bitcoin / Tether"
  },
  ...
]

Note: The exact structure may vary depending on Finnhub's API response.

Dependencies

  • External Service: Requires access to the Finnhub.io API.
  • API Key: You must configure a valid Finnhub API key in n8n credentials under the name finnhub.
  • n8n Configuration: No special environment variables are required beyond the API key setup.

Troubleshooting

Common issues:

  • Invalid API Key: If the API key is missing or incorrect, the node will fail with an authentication error. Ensure your Finnhub credentials are correctly set up in n8n.
  • Unsupported Exchange: If you specify an exchange not supported by Finnhub, the output may be empty or an error may be returned. Double-check the exchange name (e.g., "binance").
  • API Rate Limits: Finnhub enforces rate limits. Exceeding these may result in errors; consider upgrading your plan or adding delays between requests.

Common error messages:

  • "401 Unauthorized": Check your API key configuration.
  • "Exchange not found": Verify the exchange name is correct and supported.
  • "429 Too Many Requests": Slow down your request frequency.

Links and References

Discussion