Crypto APIs

Overview

This node operation prepares a transaction to transfer a Non-Fungible Token (NFT) from one address on an EVM-compatible blockchain. It constructs the necessary transaction data for sending an NFT, including details such as sender, recipient, token ID, and optional fee and nonce parameters.

This node is useful when you want to programmatically create a transaction payload for transferring NFTs without immediately broadcasting it. For example, developers can use this to prepare transactions for signing offline or to integrate with custom wallet solutions that require pre-built transaction data.

Practical examples:

• Preparing an NFT transfer transaction on Ethereum or other EVM chains before signing it with a hardware wallet.
• Creating transaction data for batch processing NFT transfers in a marketplace backend.
• Generating transaction payloads for testing or simulation purposes.

Properties

Output

The node outputs a JSON array where each item contains the prepared transaction data returned by the Crypto APIs service. This data typically includes all necessary fields to sign and broadcast the NFT transfer transaction on the specified EVM blockchain.

If binary data were involved (not indicated here), it would represent raw transaction bytes or signatures, but this node focuses on JSON transaction preparation.

Dependencies

• Requires an API key credential for accessing the Crypto APIs REST API.
• The node reads a local OpenAPI specification file (2024-12-12-final.json) bundled with the node to dynamically configure operations.
• Network connectivity to Crypto APIs endpoints is required.
• No additional environment variables are explicitly needed beyond the API authentication.

Troubleshooting

• Operation Not Found Error: If the specified operation cannot be found, ensure the "Prepare A Non Fungible Token Transfer From Address EVM" operation is correctly selected and the bundled OpenAPI spec file is intact.
• Missing Required Parameters: The node requires blockchain and network parameters at minimum. Omitting these will cause errors.
• Invalid Addresses or Token IDs: Providing incorrect or malformed addresses or token IDs may result in API errors. Validate inputs before execution.
• API Authentication Failures: Ensure the API key credential is valid and has permissions for the requested blockchain network.
• Continue On Fail Behavior: If enabled, errors per item will be returned as JSON objects with an error field instead of stopping execution.

Links and References

• Crypto APIs Documentation
• EVM NFT Transfer Concepts
• OpenAPI Specification