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 Webhooks, Crypto payments, Pix payments, account management, and checkout processes. Specifically, for the 'Webhooks' resource and 'Generate Crypto Payment' operation, it allows users to generate cryptocurrency payment requests by sending the required data to the Zendry API. This node is useful for automating payment processing workflows, managing webhook registrations, and handling cryptocurrency transactions within n8n workflows.

Use Case Examples

  1. Generating a crypto payment request by providing necessary payment details in JSON format.
  2. Registering or updating a webhook URL to receive notifications from Zendry.
  3. Listing available webhook types or existing webhooks for management purposes.

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, which should not be changed unless necessary.
Additional Fields Optional parameters to customize the request, such as generator name, document, external reference, expiration time, external link, filters, webhook URL, webhook type ID, authorization header value, and payment authorization status.
Required Fields (JSON) JSON object containing the required fields for the selected operation, as specified by the Zendry API documentation.

Output

JSON

  • json - The JSON response from the Zendry API corresponding to the requested operation, such as details of the generated crypto payment or webhook information.

Dependencies

  • Zendry API

Troubleshooting

  • Ensure the Access Token is valid and has the necessary permissions to perform the requested operation; invalid tokens will cause authentication errors.
  • The 'requestBody' must be a valid JSON string; invalid JSON will cause parsing errors and prevent the request from being sent.
  • Required parameters such as 'webhook_type_id' and 'url' for webhook registration must be provided; missing these will result in errors.
  • Check that the Base URL is correct and accessible; changing it incorrectly may cause connection failures.
  • If the node throws errors about unsupported resources or operations, verify that the selected resource and operation are supported by the node.

Links

Discussion