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 the Checkout resource, specifically listing payments in this context. It allows users to retrieve a list of payments processed through Zendry's Pix payment system, supporting optional filtering via JSON parameters. This node is useful for financial reconciliation, payment tracking, and reporting scenarios where users need to fetch payment data programmatically from Zendry.

Use Case Examples

  1. A business uses this node to automatically fetch all Pix payments received within a certain period for accounting purposes.
  2. A developer integrates this node into a workflow to monitor payment statuses and trigger follow-up actions based on payment authorization.

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; typically left as default unless a custom endpoint is required.
Additional Fields Optional parameters to refine the payment listing, such as generator name, document, external reference, expiration time, external link, JSON filters, webhook settings, and payment authorization status.
Required Fields (JSON) JSON object containing required fields for the operation as per Zendry API documentation.

Output

JSON

  • json - The JSON response from the Zendry API containing the list of payments or error details.

Dependencies

  • Zendry API access requiring a valid Bearer access token

Troubleshooting

  • Ensure the Access Token is valid and has the necessary permissions to access payment data.
  • Verify that the JSON provided in 'Required Fields' and 'Filters' is correctly formatted to avoid parsing errors.
  • Check that mandatory parameters like reference codes or IDs are provided when required by the operation.
  • Common errors include invalid token errors, malformed JSON errors, and missing required parameters. These can be resolved by validating credentials, correcting JSON syntax, and supplying all mandatory fields respectively.

Links

Discussion