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 Global API, specifically supporting the 'Checkout' resource with the 'Get by EndToEnd' operation. It retrieves checkout information by the unique 'end_to_end' identifier, which is typically used to track payment transactions. This node is useful for scenarios where you need to fetch detailed checkout or payment status information based on a transaction's end-to-end identifier, such as in payment reconciliation or transaction monitoring workflows.

Use Case Examples

  1. Retrieve checkout details by providing the 'end_to_end' identifier to track a specific payment transaction.
  2. Use in financial automation to verify payment status or details from the Zendry API using the end-to-end reference.

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.
Additional Fields Optional parameters to customize the request, such as generator name, document, external reference, expiration time, external link, filters, webhook URL and type, authorization header for webhook, and payment authorization status.
Required Fields (JSON) JSON object containing required fields for the operation as per API documentation.

Output

JSON

  • json - The JSON response from the Zendry API containing checkout details retrieved by the end_to_end identifier.

Dependencies

  • Zendry API access requiring a valid Bearer access token

Troubleshooting

  • Ensure the 'end_to_end' parameter is provided; it is mandatory for the 'Get by EndToEnd' operation and missing it will cause an error.
  • Verify that the Access Token is valid and has the necessary permissions to access the Zendry API.
  • Check that the Base URL is correct and reachable; the default is https://api.zendry.com.br and should not be changed unless necessary.
  • If the requestBody JSON is malformed, the node will throw an error indicating invalid JSON; ensure proper JSON formatting.

Links

Discussion