Zendry Global API 1.0 icon

Zendry Global API 1.0

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

Actions120

Overview

This node integrates with the Zendry API to perform various operations related to Webhooks, Payments, Pix, Account, Crypto, and Checkout services. Specifically, for the 'Webhooks' resource and 'Create Payment (Manual)' operation, it allows users to create manual Pix payments by sending a POST request to the Zendry API with the required payment details. This node is useful for automating payment creation workflows, managing webhook registrations, and handling payment-related tasks programmatically within n8n.

Use Case Examples

  1. Creating a manual Pix payment by providing payment details in JSON format.
  2. Registering a webhook URL to receive notifications from Zendry.
  3. Listing existing webhooks or payment records for monitoring and reporting.

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, webhook URL, webhook type ID, authorization header for webhook, and payment authorization status.
Required Fields (JSON) JSON object containing the required fields for the operation, such as payment details for creating a manual payment.

Output

JSON

  • json - The JSON response from the Zendry API containing the result of the requested operation, such as payment creation confirmation or webhook registration details.

Dependencies

  • Requires a valid Zendry API access token for authentication.

Troubleshooting

  • Ensure the 'requestBody' JSON is valid and correctly formatted; invalid JSON will cause errors.
  • Mandatory fields like 'webhook_type_id', 'url', 'reference_id', or 'end_to_end' must be provided for their respective operations, otherwise the node will throw an error.
  • Check that the Access Token is valid and has the necessary permissions to perform the requested operation.
  • If the API base URL is changed, verify it is correct to avoid connection errors.

Links

Discussion