Zendry Global API 1.0 icon

Zendry Global API 1.0

Acesso universal à API Zendry (Pix, Payments, Webhooks, Account, Crypto, Checkout) via AccessToken

Actions120

Receipts (Pix) → List Webhooks

AI-generated

Overview

This node integrates with the Zendry API to manage various resources including Pix receipts, payments, webhooks, accounts, crypto, and checkout operations. Specifically, for the 'Receipts (Pix)' resource with the 'List Webhooks' operation, it fetches a list of registered webhooks from the Zendry API. This is useful for monitoring and managing webhook endpoints that receive notifications about events such as payments or other Pix-related activities. Practical use cases include automating webhook management, auditing webhook configurations, or integrating webhook data into other workflows.

Use Case Examples

  1. A user wants to retrieve all webhook URLs registered in their Zendry account to verify which endpoints are active.
  2. An automation workflow needs to fetch webhook details to dynamically update or log webhook configurations.

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 that can be used to filter or modify the request, such as generator name, document, external reference, expiration time, external link, filters in JSON format, webhook URL, webhook type ID, authorization header value, and authorization status.
Required Fields (JSON) JSON object containing required fields for the operation as per the API documentation.

Output

JSON

  • json - The JSON response from the Zendry API containing the list of webhooks and their details.

Dependencies

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

Troubleshooting

  • Common issues include invalid or expired access tokens resulting in authentication errors. Ensure the Access Token is valid and has the necessary permissions.
  • Malformed JSON in the 'Required Fields (JSON)' or 'Filters (JSON)' properties can cause parsing errors. Validate JSON syntax before execution.
  • Missing required parameters such as 'webhook_type_id' or 'url' for certain webhook operations will throw errors. Verify all mandatory fields are provided.

Links

Discussion