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 Webhooks, Pix payments, receipts, account information, crypto transactions, and checkout processes. Specifically, for the 'Simulate QRCode Payment' operation under the 'Webhooks' resource, it simulates a payment for a given QR code reference ID. This is useful for testing payment workflows and webhook notifications without actual transactions. Practical examples include simulating a Pix payment to verify webhook handling or testing payment status updates in an automated workflow.

Use Case Examples

  1. Simulate a QR code payment by providing a reference ID to test webhook notifications.
  2. Use the node to simulate payments for Pix QR codes to validate payment processing logic in your system.

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; usually left as default unless a custom endpoint is needed.
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 required fields for the specific operation, such as the reference ID for simulating a QR code payment.

Output

JSON

  • json - The JSON response from the Zendry API corresponding to the requested operation, including payment simulation results and webhook responses.

Dependencies

  • Requires a valid Zendry API access token for authentication.

Troubleshooting

  • Ensure the 'accessToken' is valid and has the necessary permissions to perform the operation.
  • For the 'Simulate QRCode Payment' operation, the 'reference_id' must be provided either in the required JSON fields or additional fields; otherwise, an error is thrown.
  • The 'requestBody' must be a valid JSON string; invalid JSON will cause a parsing error.
  • If the API endpoint or operation is unsupported or incorrectly specified, the node will throw an error indicating the unsupported resource or operation.

Links

Discussion