Crypto APIs icon

Crypto APIs

Interact with Crypto APIs REST API

Actions113

Overview

This node interacts with the Crypto APIs REST API to perform various blockchain-related operations. Specifically, for the "addresses-historical" resource and the "Activate Synced Address" operation, it activates a previously synced address on a specified blockchain network. This is useful in scenarios where you want to resume or enable tracking of historical data for a wallet address that was previously synced but inactive.

Practical examples include:

  • Reactivating monitoring of a wallet address's historical transactions after a pause.
  • Resuming data synchronization for an address on a specific blockchain and network to continue analytics or auditing.

Properties

Name Meaning
address The wallet address to activate syncing for.
blockchain The blockchain on which the address exists (e.g., Ethereum, Bitcoin).
network The specific network of the blockchain (e.g., mainnet, testnet).
context Optional context string to correlate responses with requests (for user tracking).
JSON Body Additional parameters as a JSON object to customize the activation request (empty by default).

Output

The node outputs a JSON array containing the response from the Crypto APIs service regarding the activation status of the synced address. The exact structure depends on the API response but typically includes details about the address, its activation state, and any metadata returned by the service.

No binary data output is produced by this operation.

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 resolve operation details.

Troubleshooting

  • Common issues:

    • Incorrect or missing required parameters such as address, blockchain, or network will cause errors.
    • Network connectivity problems or invalid API credentials will prevent successful API calls.
    • If the operation ID cannot be found in the specification file, the node throws an error indicating the operation is not found.
  • Error messages:

    • "Operation <operationName> not found": Indicates a mismatch or misconfiguration in the operation name; verify the selected operation.
    • API errors returned from Crypto APIs (e.g., invalid address format, unsupported blockchain/network) will be passed through and can be inspected in the output if "Continue On Fail" is enabled.

Links and References

Discussion