Crypto APIs icon

Crypto APIs

Interact with Crypto APIs REST API

Actions113

Overview

This node interacts with a cryptocurrency API service to synchronize historical address data on various blockchains. Specifically, the "Sync Address" operation under the "addresses-historical" resource allows users to request synchronization of wallet address information for a specified blockchain and network.

Common scenarios include:

  • Keeping an up-to-date record of wallet addresses and their transaction history.
  • Triggering backend processes that require refreshed address data.
  • Integrating blockchain address data synchronization into automated workflows.

For example, a user might use this node to sync a Bitcoin address on the mainnet to ensure their database reflects the latest transactions and balances.

Properties

Name Meaning
blockchain The blockchain network to target (e.g., Bitcoin, Ethereum).
network The specific network within the blockchain (e.g., mainnet, testnet).
context Optional string to pass additional context or metadata for the sync request.
JSON Body A collection of optional fields:
- address The wallet address to synchronize.
- callbackUrl A URL to receive asynchronous notifications or callbacks related to the sync operation.

Output

The node outputs a JSON array containing the response from the API after requesting the address synchronization. The exact structure depends on the API's response but generally includes details about the sync status or any relevant metadata returned by the service.

No binary data output is produced by this node.

Dependencies

  • Requires an active connection to the external Crypto APIs REST API service.
  • Needs an API authentication token configured in n8n credentials to authorize requests.
  • Uses a local JSON schema file (2024-12-12-final.json) to map operations and parameters statically.

Troubleshooting

  • Operation not found error: If the specified operation cannot be found, verify that the "Sync Address" operation is correctly selected and supported by the current version of the node.
  • Missing required parameters: Ensure that mandatory fields like blockchain and network are provided; otherwise, the API call will fail.
  • API request failures: Network issues or invalid API credentials can cause errors. Confirm that the API key is valid and the service endpoint is reachable.
  • Callback URL issues: If using callbackUrl, ensure it is a valid and accessible URL to receive asynchronous updates.

Links and References

Discussion