Keitaro icon

Keitaro

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

Actions72

Overview

This node integrates with the Keitaro API to perform various operations on different 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 resource "Источник" (Source), it supports operations including getting, updating, and deleting a source. The node is useful for automating management of marketing and traffic data within Keitaro, such as updating source details or retrieving source information. For example, a user can update the JSON data of a source by providing the source ID and the new data in JSON format.

Use Case Examples

  1. Updating a source's data by providing the source ID and new JSON data.
  2. Retrieving information about a specific source by its ID.
  3. Deleting a source by its ID.

Properties

Name Meaning
ID Источника The unique identifier of the source to be used for get, update, or delete operations.
Данные Источника The JSON-formatted data representing the source details, required for create and update operations.

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 the API key masked.
  • resource - The resource type involved in the operation (e.g., source).
  • operation - The operation performed (e.g., update).
  • success - Indicates if the operation was successful (true for create, update, delete).
  • data - The data returned from the Keitaro API after the operation.
  • error - If an error occurred, this field contains error details including message, stack, resource, operation, URL, status, statusText, and response data.

Dependencies

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

Troubleshooting

  • Common issues include missing or invalid source ID for operations that require it, resulting in errors indicating the ID is required.
  • Errors may occur if the API key or domain is not set in the credentials, with messages prompting to verify these settings.
  • API errors from Keitaro are surfaced with status codes and messages; users should check the API key validity and permissions.
  • For 'getAll' operations on clicks, required parameters like interval or date range must be provided, otherwise an error is thrown.

Discussion