Overview

This node integrates with the Keitaro API to manage various resources such as campaigns, streams, landings, offers, traffic, users, blacklists, bots, postbacks, sources, conversions, domains, clicks, filters, settings, logs, statistics, and groups. It supports operations like creating, updating, deleting, and retrieving data for these resources. Specifically, for the "Настройки" (Settings) resource with the "Создать" (Create) operation, the node allows users to create new settings by providing the settings data in JSON format. This node is useful for automating and managing marketing campaign data and configurations within the Keitaro platform, enabling seamless API interactions for data manipulation and retrieval.

Use Case Examples

1. Creating new settings in Keitaro by providing JSON data for configuration.
2. Automating campaign management by creating, updating, or deleting resources via API calls.
3. Fetching detailed reports and logs for analysis and optimization of marketing efforts.

Properties

Output

JSON

• request
  • url - The URL of the API request made to Keitaro.
  • method - The HTTP method used for the API request.
  • headers - Headers sent with the API request, with sensitive data like API keys masked.
• resource - The resource type involved in the operation (e.g., settings).
• operation - The operation performed on the resource (e.g., create).
• success - Indicates if the operation was successful (true for create, update, delete).
• data - The data returned from the Keitaro API after the operation, typically the created or updated resource details.
• error - If an error occurs, this field contains error details including message, stack trace, HTTP status, and response data.

Dependencies

• Requires an API key credential for Keitaro API authentication.
• Needs the domain URL of the Keitaro instance for API requests.

Troubleshooting

• Ensure the API key and domain are correctly set in the node credentials; missing or incorrect credentials will cause authentication errors.
• For create operations, the JSON data must be valid and non-empty; otherwise, the node throws an error indicating missing data.
• The node only supports the 'getAll' operation for the 'stats' resource; using other operations with 'stats' will result in an error.
• If the API returns an error status, the node throws an error with the API's message; check the API response for details.
• When using the 'click' resource with 'getAll', at least one parameter (interval, date range, or limit) must be specified to avoid errors.