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, Pix payments, receipts, accounts, crypto, and checkout processes. Specifically, for the 'Webhooks' resource and 'Create Checkout (Pix)' operation, it allows users to create a Pix checkout by sending a POST request to the Zendry API. This is useful for automating payment processing and webhook management in financial applications, enabling seamless creation of Pix checkouts with optional parameters such as generator details, expiration time, external references, and webhook configurations.

Use Case Examples

  1. Creating a Pix checkout for an e-commerce transaction to enable customers to pay via Pix QR code.
  2. Registering a webhook URL to receive notifications about payment status changes.
  3. Listing all registered webhooks to monitor active integrations.

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 for webhook, and payment authorization status.
Required Fields (JSON) JSON object containing required fields for the operation, as specified by the Zendry API documentation.

Output

JSON

  • json - The JSON response from the Zendry API containing the result of the requested operation, such as details of the created Pix checkout or webhook registration.

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.
  • Verify that the 'requestBody' JSON is correctly formatted; invalid JSON will cause errors.
  • Mandatory fields like 'webhook_type_id' and 'url' must be provided for webhook registration operations; missing these will throw 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