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 operations related to Webhooks, Payments, Pix, Account, Crypto, and Checkout services. Specifically, for the 'Webhooks' resource and 'Create Payment (DICT)' operation, it allows users to create a payment using the DICT initiation type by sending a POST request to the Zendry API. This node is useful for automating payment creation workflows, managing webhook registrations, and handling other financial transactions via Zendry's API.

Use Case Examples

  1. Creating a payment with DICT initiation type by providing required JSON fields and optional parameters like authorization status.
  2. Registering a webhook by specifying the webhook type ID and URL for notifications.
  3. Listing all webhook types or existing webhooks for monitoring and management.

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 operation as per the Zendry API documentation.

Output

JSON

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

Dependencies

  • Requires a valid Zendry API access token for authentication.

Troubleshooting

  • Ensure the 'requestBody' JSON is valid and contains all required fields; invalid JSON will cause errors.
  • Mandatory parameters like 'webhook_type_id' and 'url' must be provided for webhook registration operations.
  • Check that the access token is valid and has the necessary permissions to perform the requested operation.
  • If the node throws errors about unsupported resources or operations, verify that the resource and operation names are correctly set.

Discussion