Actions72
- Кампания Actions
- Лендинг Actions
- Оффер Actions
- Клик Actions
- Настройки Actions
- Пользователь Actions
- Блэклист Actions
- Бот Actions
- Постбэк Actions
- Источник Actions
- Конверсия Actions
- Статистика Actions
- Группа Actions
- Поток Actions
- Фильтр Actions
- Лог Actions
- Домен Actions
Overview
This node integrates with the Keitaro API to manage various resources such as campaigns, streams, landings, offers, users, blacklists, and more. Specifically, for the 'blacklist' resource and 'update' operation, it updates an existing blacklist entry with new data provided in JSON format. This node is useful for automating the management of blacklist entries in Keitaro, such as updating IP addresses or other blacklist criteria programmatically.
Use Case Examples
- Updating a blacklist entry to add or modify IP addresses or other blacklist parameters in Keitaro.
- Automating blacklist management as part of a larger workflow to maintain campaign quality.
Properties
| Name | Meaning |
|---|---|
| ID Блэклиста | The ID of the blacklist entry to update, required for update operations. |
| Данные Блэклиста | The JSON-formatted data representing the blacklist entry to update, required for create and update operations. |
Output
JSON
requesturl- 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 API keys masked.
resource- The resource type involved in the operation, e.g., 'blacklist'.operation- The operation performed, e.g., 'update'.success- Indicates if the operation was successful (true for update success).data- The data returned from the Keitaro API after the update operation.
Dependencies
- Keitaro API with domain and API key credentials required for authentication.
Troubleshooting
- Ensure the 'blacklistId' is provided and valid for update operations; missing or invalid IDs will cause errors.
- The 'blacklistData' JSON must be well-formed and contain the necessary fields for the update; invalid JSON or empty data will cause errors.
- API credentials (domain and API key) must be correctly configured; missing credentials will prevent API calls.
- Check API response status codes and messages for specific errors returned by Keitaro, such as authorization failures or invalid data.
Links
- Keitaro API Documentation - Official documentation for the Keitaro API, useful for understanding resource structures and operations.