Avito icon

Avito

Взаимодействие с API Авито для бизнеса

Actions29

Overview

This node integrates with the Avito API to retrieve various types of data related to Avito listings (Объявления), promotions, ratings, and autoload features. Specifically for the resource "Объявление" (Item) and operation "Счетчики Объявлений" (Item Counters / Stats Shallow), it fetches statistical counters about specified Avito listings over a given time period.

Typical use cases include:

  • Monitoring user engagement metrics on one or more Avito listings.
  • Analyzing trends in views, contacts, and favorites for listings.
  • Grouping statistics by day, week, or month to observe performance over time.

Practical example:

  • A real estate agent wants to track how many unique users viewed or contacted their property ads on Avito during the last month, grouped by week, to optimize their advertising strategy.

Properties

Name Meaning
ID Пользователя (userId) The numeric ID of the Avito user whose listings are being queried. Required.
ID Объявлений (itemIds) Comma-separated list of listing IDs to retrieve stats for. Required for some operations.
Дата Начала (dateFrom) Start date (inclusive) of the period for which to fetch statistics. Required for some ops.
Дата Окончания (dateTo) End date (inclusive) of the period for which to fetch statistics. Max range is 270 days.
Показатели (statsFields) Set of counters/statistics to retrieve. Options include:
- Избранное (Устаревшее) [Deprecated]
- Контакты (Устаревшее) [Deprecated]
- Просмотры (Устаревшее) [Deprecated]
- Уникальное Избранное (unique favorites count)
- Уникальные Контакты (unique contacts count)
- Уникальные Просмотры (unique views count)
Группировка (periodGrouping) How to group the statistics over time:
- По Дням (day): no grouping, daily stats
- По Неделям (week): sum stats weekly
- По Месяцам (month): sum stats monthly

Output

The node outputs an array of JSON objects, each corresponding to an input item processed. Each output JSON contains the requested statistical counters for the specified listings and period.

The structure typically includes:

  • The listing IDs queried.
  • The requested counters (e.g., unique views, unique contacts, unique favorites).
  • The values of these counters, optionally grouped by the selected period (day/week/month).

If binary data were involved (not indicated here), it would be summarized accordingly, but this node focuses on JSON statistical data.

Dependencies

  • Requires an API key credential for authenticating with the Avito API.
  • The node depends on internal routing utilities (RouterUtils) to dispatch requests based on resource and operation.
  • No additional external dependencies beyond the Avito API and n8n core modules.

Troubleshooting

  • Common issues:

    • Providing invalid or expired API credentials will cause authentication errors.
    • Requesting statistics for non-existent or unauthorized listing IDs may return errors or empty results.
    • Exceeding the maximum allowed date range (270 days) will likely result in an error.
    • Using deprecated stats fields may not return expected data; prefer unique counters instead.

  • Error messages:

    • "Unknown resource: ..." — indicates an unsupported resource was selected.
    • API errors from Avito will be passed through; check the message for details.
    • If continueOnFail is enabled, errors per item will be returned as JSON with an error field.

  • Resolutions:

    • Verify API credentials and permissions.
    • Ensure listing IDs and user IDs are correct.
    • Respect the date range limits.
    • Use updated stats fields as recommended.

Links and References

Discussion