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 Receipts (Pix), Payments, Webhooks, Account, Crypto, and Checkout services. Specifically, for the 'Receipts (Pix)' resource and 'List Webhook Types' operation, it fetches the list of available webhook types from the Zendry API. This is useful for users who want to manage or monitor webhook events related to their Pix transactions or other services provided by Zendry. For example, a user can retrieve webhook types to configure notifications for payment events or other triggers.

Use Case Examples

  1. A user wants to list all webhook types available in their Zendry account to set up appropriate webhook listeners for Pix payment notifications.
  2. A developer integrates this node in an automation workflow to dynamically fetch webhook types and register new webhooks based on the retrieved types.

Properties

Name Meaning
Access Token A valid Bearer access token for authenticating requests to the Zendry API.
Base URL The base URL of the Zendry API; usually left as default unless a custom endpoint is needed.
Additional Fields Optional parameters that can be used to provide extra data depending on the operation, such as generator name, document, external references, filters, webhook URL, webhook type ID, authorization header value, and authorization status.
Required Fields (JSON) JSON object containing required fields for the specific operation, as per the API documentation.

Output

JSON

  • json - The JSON response from the Zendry API containing the list of webhook types or other requested data.

Dependencies

  • Zendry API access requiring a valid Bearer access token.

Troubleshooting

  • Ensure the Access Token is valid and has the necessary permissions to access the Zendry API.
  • Verify that the Base URL is correct and reachable; usually, the default URL should not be changed unless necessary.
  • For JSON input fields like 'Required Fields (JSON)' and 'Filters (JSON)', ensure the JSON is valid to avoid parsing errors.
  • Mandatory parameters such as 'webhook_type_id' and 'url' must be provided for operations that require them, otherwise the node will throw an error indicating the missing parameter.

Links

Discussion