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 interacts with the Zendry API to perform various operations related to Pix receipts, payments, webhooks, account information, cryptocurrency transactions, and checkout processes. Specifically, for the 'Receipts (Pix)' resource and the 'Simulate Crypto Receivement' operation, it sends a POST request to simulate the receipt of cryptocurrency payments. This node is useful for automating and integrating financial workflows involving Pix and crypto transactions, such as testing crypto payment receipt simulations or managing Pix QR codes and payments.

Use Case Examples

  1. Simulate a cryptocurrency receivement to test payment processing workflows.
  2. Create and manage Pix QR codes for instant payments.
  3. Register and manage 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, 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 and type, authorization header for webhooks, and payment authorization status.
Required Fields (JSON) JSON object containing the required fields for the operation, as specified by the Zendry API documentation.

Output

JSON

  • json - The JSON response from the Zendry API corresponding to the requested operation, containing data such as simulated crypto receivement details or other resource-specific information.

Dependencies

  • Requires a valid Bearer access token for Zendry API authentication.

Troubleshooting

  • Ensure the 'Access Token' is valid and has the necessary permissions to perform the requested operation.
  • The 'requestBody' must be a valid JSON string; invalid JSON will cause an error.
  • Mandatory parameters like 'reference_id' or 'end_to_end' must be provided for certain operations; missing these will result in errors.
  • Check the 'Base URL' if the API endpoint is unreachable, but it should generally remain as the default unless Zendry changes their API URL.

Links

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

Discussion