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 API to perform various operations related to payments, Pix QR codes, webhooks, accounts, cryptocurrencies, and checkout processes. Specifically, for the 'Checkout' resource and 'Create Payment (Manual)' operation, it allows users to manually create a payment via the Zendry API by sending a POST request with the required payment details. This node is useful for automating payment creation workflows, managing payment data, and integrating payment processing into broader automation scenarios.

Use Case Examples

  1. Creating a manual payment entry in Zendry for a customer transaction.
  2. Automating payment processing by sending payment details from an external system to Zendry.
  3. Using additional optional fields to customize payment creation, such as setting authorization status or adding external references.

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 payment creation, such as generator name, document, external reference, expiration time, external link, filters, webhook settings, and authorization status.
Required Fields (JSON) JSON object containing the required fields for the payment creation operation, as specified by the Zendry API documentation.

Output

JSON

  • json - The JSON response from the Zendry API containing details of the created payment or error information.

Dependencies

  • Zendry API access requiring a valid Bearer access token

Troubleshooting

  • Ensure the Access Token is valid and has the necessary permissions to perform payment creation.
  • Verify that the JSON provided in 'Required Fields (JSON)' is correctly formatted and includes all mandatory fields as per Zendry API documentation.
  • Check that the Base URL is correct and accessible; use the default unless a custom endpoint is required.
  • If the node throws errors about missing required fields (e.g., reference_code, idempotent_id), verify that these fields are included in the input JSON or additional fields as needed.

Links

Discussion