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 manage various payment-related operations, specifically supporting the creation of manual Pix payments under the Payments (Pix Out) resource. It allows users to create payments manually by sending required and optional parameters to the Zendry API. This node is useful for automating payment processing workflows, such as generating Pix payments with custom details, tracking payments via external references, and managing payment authorization status.

Use Case Examples

  1. Creating a manual Pix payment by providing required payment details in JSON format along with optional fields like generator name and document for better tracking.
  2. Automating payment creation in a financial system where Pix payments are a common transaction method, enabling seamless integration with Zendry's payment API.

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 payment creation, such as generator name, generator document, external reference, expiration time, external link, filters, webhook settings, and payment authorization status.
Required Fields (JSON) JSON object containing the required fields for the payment creation operation as per Zendry API documentation.

Output

JSON

  • json - The JSON response from the Zendry API containing details of the created payment or the result of the requested operation.

Dependencies

  • Zendry API (requires a valid Bearer access token)

Troubleshooting

  • Ensure the Access Token is valid and has the necessary permissions to perform payment operations on the Zendry API.
  • The 'requestBody' must be a valid JSON string; invalid JSON will cause an error.
  • Required fields for the payment creation must be provided; missing mandatory fields will result in errors.
  • For operations requiring specific identifiers (e.g., reference_code, idempotent_id), ensure these are provided either in the requestBody or additional fields.
  • If the API base URL is changed, verify it is correct to avoid connection errors.

Links

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

Discussion