IyzicoInstall

Overview

The node integrates with the Iyzico iyzilink API to manage iyzilink products (payment links). It supports operations such as creating, updating, deleting, retrieving details, listing multiple links, and updating the status of these payment links.

This node is useful for merchants or businesses who want to programmatically manage their payment links on Iyzico's platform. For example, a merchant can create new payment links for products, update product details, list all available payment links with pagination, or deactivate/reactivate links as needed.

Practical examples:

• Automatically generate payment links for new products added in an e-commerce system.
• Periodically fetch and display a paginated list of active payment links.
• Update the status of a payment link based on inventory or promotional campaigns.

Properties

Note: The provided properties focus on the "List Links" operation, which requires Page and Count as mandatory inputs, and optionally accepts additional fields like Conversation ID and Locale.

Output

The node outputs JSON data representing the API response from Iyzico. For the "List Links" operation, the output JSON contains a paginated list of iyzilink products with their details as returned by the API.

The structure typically includes:

• Status of the API call (e.g., "success").
• An array of payment link products with their attributes (such as name, price, currency, description, token, status, etc.).
• Pagination metadata (page number, count, total items) if provided by the API.

No binary data output is produced by this node.

Dependencies

• Requires an API key credential and secret key credential for authenticating with the Iyzico API.
• The node uses HMAC SHA256 signature authentication with the provided credentials.
• Supports both sandbox and production environments, selectable via the credential configuration.
• No other external dependencies beyond standard HTTP requests.

Troubleshooting

• Authentication failed: If the node throws an error about authentication failure, verify that the API key and secret key are correct and correspond to the selected environment (sandbox or production). Ensure the HMAC SHA256 signing method is correctly applied.
• API errors: If the API returns an error status, the node surfaces the error message and group. Check the error message for issues such as invalid parameters or rate limits.
• Pagination issues: When listing links, ensure that Page and Count values are positive integers to avoid unexpected results.
• Network or connectivity problems: Verify network access to the Iyzico API endpoints.

If the node is set to continue on fail, errors will be included in the output JSON with details for easier debugging.

Links and References

• Iyzico API Documentation
• Iyzico iyzilink Product Management
• HMAC SHA256 Authentication

This summary is based solely on static analysis of the provided source code and property definitions.