Zendry Global API 1.0 icon

Zendry Global API 1.0

Acesso universal à API Zendry (Pix, Payments, Webhooks, Account, Crypto, Checkout) via AccessToken

Actions120

Account → Create Payment (Manual)

AI-generated

Overview

This node integrates with the Zendry API to perform various operations related to accounts, payments, Pix QR codes, webhooks, crypto, and checkout services. Specifically, for the 'Account' 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 Pix payments, and integrating payment processing into broader automation scenarios.

Use Case Examples

  1. Manually create a Pix payment by providing payment details in JSON format.
  2. Automate payment processing by integrating Zendry's payment creation API into an n8n workflow.

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 to include in the payment creation request, 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 other requested data.

Dependencies

  • Requires a valid Zendry API access token for authentication.

Troubleshooting

  • Ensure the 'requestBody' JSON is valid and correctly formatted; invalid JSON will cause errors.
  • Mandatory fields like 'reference_id' or 'end_to_end' must be provided for certain operations; missing these will throw errors.
  • Check that the access token is valid and has the necessary permissions to perform the requested operation.
  • If the base URL is changed, verify it points to a valid Zendry API endpoint.

Discussion