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 Global API to manage various financial operations related to Pix receipts, payments, webhooks, accounts, crypto, and checkout. Specifically, for the 'Receipts (Pix)' resource and 'Remove Webhook' operation, it allows users to remove a registered webhook by specifying the webhook type ID. This is useful for managing webhook subscriptions and stopping notifications for certain events. Practical use cases include automating webhook management in payment processing workflows and ensuring that outdated or unnecessary webhooks are cleanly removed from the system.

Use Case Examples

  1. Removing a webhook subscription for a specific webhook type ID to stop receiving notifications related to Pix receipts.
  2. Automating webhook cleanup in a payment processing system to maintain only active and relevant webhook endpoints.

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 provided for various operations, including webhook management. For the Remove Webhook operation, the key field is 'webhook_type_id' which specifies the ID of the webhook type to remove.
Required Fields (JSON) JSON object containing required fields for the operation as per the API documentation. For Remove Webhook, this is typically empty or minimal.

Output

JSON

  • json - The JSON response from the Zendry API after attempting to remove the webhook, containing success or error details.

Dependencies

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

Troubleshooting

  • Common issues include missing or invalid 'webhook_type_id', which is required to identify the webhook to remove. The node will throw an error if this field is not provided.
  • Invalid or expired access tokens will cause authentication failures. Ensure the Access Token is valid and has the necessary permissions.
  • Malformed JSON in the 'Required Fields (JSON)' input will cause parsing errors. Ensure the JSON is valid if used.

Discussion