Keitaro icon

Keitaro

Работа с API Keitaro
Join our community

Actions72

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. Specifically, for the 'filter' resource and 'delete' operation, it deletes a filter by its ID. This node is useful for automating the management of marketing and tracking data within Keitaro, such as creating, updating, retrieving, and deleting filters and other entities.

Use Case Examples

  1. Deleting a filter by its ID to clean up unused or obsolete filters in Keitaro.
  2. Automating the update of campaign filters based on dynamic criteria.
  3. Retrieving all filters to audit or analyze filtering rules applied in Keitaro.

Properties

Name Meaning
ID Фильтра The unique identifier of the filter to be deleted. Required for 'get', 'update', and 'delete' operations on the filter resource.

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., 'filter'.
  • operation - The operation performed, e.g., 'delete'.
  • success - Boolean indicating if the operation was successful (true for delete).
  • data - The data returned from the Keitaro API after the operation, typically confirmation of deletion or details of the affected filter.

Dependencies

  • Requires an API key credential for Keitaro API access, including domain and API key.

Troubleshooting

  • Ensure the 'filterId' is provided and correctly formatted; missing or invalid IDs will cause errors.
  • Verify that the API key and domain credentials are correctly set up and valid; missing credentials will prevent API access.
  • Check for API response errors indicating permission issues or resource not found, which may require verifying user permissions or filter existence.
  • For 'delete' operations, confirm the filter ID matches an existing filter to avoid 'not found' errors.

Links

Discussion