Avito icon

Avito

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

Actions29

Overview

This node integrates with the Avito API to retrieve various data related to Avito's services. Specifically, for the resource Автозагрузка (Autoload), and the operation 📊 Отчеты: Список Всех (Reports: List All), it fetches paginated reports about autoload processes.

Typical use cases include:

  • Automating the retrieval of all autoload reports from Avito for analysis or monitoring.
  • Fetching specific pages of reports when only a subset is needed.
  • Using pagination options to control the volume of data fetched, which is useful in workflows that process large datasets incrementally.
  • Monitoring the status of autoload reports (processing, finished, failed) to trigger further actions based on report completion.

For example, a user might configure this node to fetch all available autoload reports, then filter those with status "finished" to download associated files or generate summaries.

Properties

Name Meaning
Номер Страницы (page) Page number to fetch, starting from 1. Used to navigate through paginated reports.
Количество На Странице (perPage) Number of reports per page, between 1 and 200. Controls how many reports are returned in one request.
Включить Автоматическую Пагинацию (enablePagination) Whether to automatically fetch all reports by performing multiple requests across pages. If enabled, the node will paginate through results until all reports are retrieved or limits are reached.
Тип Пагинации (paginationType) Pagination mode when automatic pagination is enabled:
• Получить Все Отчеты (all): fetch all available reports until no more pages.
• Лимит Страниц (limit): limit the number of pages fetched to a maximum value.
Максимум Страниц (maxPages) Maximum number of pages to fetch when pagination type is "limit". Acts as a safeguard against infinite loops. Each page can contain up to 200 reports.
Включить Задержку Запросов (enableDelay) Whether to add a delay between consecutive requests during pagination. Helps avoid hitting API rate limits or being blocked.
Задержка (мс) (requestDelay) Delay duration in milliseconds between requests when delay is enabled. Recommended to be 200 ms or more to reduce risk of API blocking.
📊 Информация об отчетах автозагрузки (reportsInfoNotice) Informational notice describing the structure and statuses of autoload reports:
• report_id: unique report ID
• started_at, finished_at: timestamps
• status: processing, finished, or failed
• section_stats, listing_fees: detailed stats
• feeds_urls: links to report files

Output

The node outputs an array of JSON objects representing autoload reports. Each report object includes fields such as:

  • report_id: Unique identifier of the report.
  • started_at: Timestamp when the autoload process started.
  • finished_at: Timestamp when the autoload process finished.
  • status: Current status of the autoload report; possible values are processing, finished, or failed.
  • section_stats: Statistics about different sections within the report.
  • listing_fees: Information about any fees charged.
  • feeds_urls: URLs linking to downloadable report files.

If pagination is enabled and multiple pages are fetched, the output aggregates all reports into a single array.

The node does not output binary data for this operation.

Dependencies

  • Requires an API authentication token credential configured in n8n to access the Avito API.
  • The node depends on the Avito API endpoints for fetching autoload reports.
  • Proper network connectivity and valid credentials are necessary.
  • Optional delays between requests can be configured to comply with API rate limits.

Troubleshooting

  • Common issues:

    • Exceeding API rate limits may cause request failures or temporary blocks. Enabling request delay (enableDelay) with a suitable delay (e.g., 200 ms) can mitigate this.
    • Requesting pages beyond the available range may return empty results or errors.
    • Incorrect pagination parameters (e.g., page less than 1 or perPage outside 1-200) will likely cause validation errors.
    • Missing or invalid API credentials will prevent successful API calls.

  • Error messages:

    • "Unknown resource": Occurs if the resource parameter is set incorrectly. Ensure the resource is set to "autoload" for this operation.
    • API errors related to authentication or permissions indicate issues with the provided API key or token.
    • Network errors suggest connectivity problems or incorrect endpoint configuration.

  • Resolutions:

    • Verify API credentials and permissions.
    • Use valid pagination parameters within allowed ranges.
    • Enable delays between requests if encountering rate limiting.
    • Limit the number of pages fetched to avoid excessive load or timeouts.

Links and References

Discussion