Zendry Global API 1.0 icon

Zendry Global API 1.0

Acesso universal à API Zendry (Pix, Payments, Webhooks, Account, Crypto, Checkout) via AccessToken

Actions120

Overview

This node integrates with the Zendry API to perform various operations related to payments, Pix transactions, webhooks, account management, cryptocurrency, and checkout processes. Specifically, for the 'Payments (Pix Out)' resource and the 'Generate Crypto Wallet' operation, it sends a POST request to the Zendry API to generate a new cryptocurrency wallet. This node is useful for automating payment workflows, managing crypto wallets, and handling Pix payment operations within an n8n workflow environment.

Use Case Examples

  1. Generating a crypto wallet for a user to receive payments in cryptocurrency.
  2. Automating the creation of Pix payment requests and managing their lifecycle.
  3. Registering and managing webhooks for payment notifications.

Properties

Name Meaning
Access Token A valid Bearer access token for authenticating with the Zendry API.
Base URL The base URL of the Zendry API, defaulting to https://api.zendry.com.br.
Additional Fields Optional parameters to customize the request, such as generator name, document, external reference, expiration time, external link, filters, webhook URL and type, authorization header for webhook, and payment authorization status.
Required Fields (JSON) JSON object containing required fields for the specific operation as per the Zendry API documentation.

Output

JSON

  • json - The JSON response from the Zendry API containing the result of the requested operation, such as the generated crypto wallet details.

Dependencies

  • Zendry API access requiring a valid Bearer access token.

Troubleshooting

  • Ensure the Access Token is valid and has the necessary permissions to perform the requested operation.
  • Verify that the JSON provided in 'Required Fields (JSON)' is correctly formatted and contains all mandatory fields as per the Zendry API documentation.
  • Check that required parameters like 'webhook_type_id', 'url', 'reference_id', or 'end_to_end' are provided when needed for specific operations to avoid errors.
  • If the node throws a 'requestBody deve ser um JSON válido' error, confirm that the JSON input is valid and properly formatted.

Links

  • Zendry API Documentation - Official documentation for the Zendry API, detailing endpoints, parameters, and usage examples.

Discussion