Crypto APIs icon

Crypto APIs

Interact with Crypto APIs REST API

Actions113

Overview

This node interacts with the Crypto APIs REST API to retrieve various cryptocurrency-related data. Specifically, for the "Market Data & Prices" resource and the "List Supported Assets" operation, it fetches a list of supported assets from the market data endpoint. This can be useful for applications that need to display or process available cryptocurrencies and fiat currencies supported by the API.

Practical examples include:

  • Displaying a list of all supported crypto and fiat assets in a portfolio management app.
  • Filtering assets by type (crypto or fiat) for trading or analysis tools.
  • Paginating through large asset lists using limit and offset parameters.

Properties

Name Meaning
context (Optional) Context parameter to filter or specify the environment or use case.
limit (Optional) Maximum number of assets to return in the response (pagination control).
offset (Optional) Number of assets to skip before starting to collect the result set (pagination).
type (Optional) Filter assets by type. Possible values: fiat (fiat currencies), crypto (cryptocurrencies).

Output

The node outputs an array of JSON objects representing the supported assets retrieved from the Crypto APIs service. Each object typically contains details about an asset such as its symbol, name, type, and other metadata provided by the API.

If the API supports binary data output for this operation (not indicated here), the node would handle it accordingly, but based on the static code and operation, the output is purely JSON.

Dependencies

  • Requires an active connection to the Crypto APIs REST API.
  • Needs an API key credential configured in n8n to authenticate requests.
  • The node reads a local OpenAPI specification file (2024-12-12-final.json) bundled with the node to dynamically build request paths and parameters.
  • Uses internal helper functions to make HTTP requests to the Crypto APIs endpoints.

Troubleshooting

  • Operation not found error: If the specified operation is not recognized, ensure the operation name matches exactly one of the supported operations in the node's dropdown.
  • Invalid or missing API credentials: The node requires valid API authentication; verify that the API key credential is correctly set up.
  • Parameter errors: Providing invalid values for limit, offset, or type may cause API errors. Use appropriate types and allowed values.
  • Network issues: Connectivity problems to the Crypto APIs service will cause request failures.
  • To handle errors gracefully, enable the "Continue On Fail" option in the node settings to capture errors in the output JSON instead of stopping execution.

Links and References

Discussion