Avito icon

Avito

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

Actions29

Overview

This node integrates with the Avito API to facilitate business operations related to Avito's platform. Specifically, the "Автозагрузка" (Autoload) resource with the operation "🚀 Ручная Загрузка Файла" (Manual File Upload) allows users to upload a file linked to their profile for bulk publishing or activation of listings.

This operation is useful when you want to perform a full upload of large catalogs of listings without being limited by the usual publication limits set in the profile settings. It is designed to handle files in formats like XLS, XLSX, CSV, or XML that are accessible via HTTP/HTTPS URLs tied to the user's profile.

Practical examples:

  • A real estate agency wants to upload a large catalog of property listings at once.
  • An automotive dealer needs to activate all valid ads from a prepared spreadsheet file.
  • Businesses managing inventory can automate bulk updates bypassing normal API rate limits on publications.

Properties

Name Meaning
📤 Загрузка файла по ссылке привязанной к профилю:
• Файл должен быть доступен к загрузке в момент запроса.
• Формат файла: XLS/XLSX/CSV/XML

⚠️ ВАЖНЫЕ ОГРАНИЧЕНИЯ:
• Лимит частоты: МАКСИМУМ 1 ЗАПРОС В ЧАС
• При превышении лимита API вернет ошибку
• Планируйте запуски заранее

🚀 Особенности загрузки:
• ИГНОРИРУЕТ лимиты публикаций из настроек профиля
• ВСЕ валидные объявления из файла будут опубликованы или активированы
• Подходит для полной загрузки больших каталогов

🔧 Предварительная настройка:
1. Настройте URL файла через "Создать/Обновить Профиль"
2. Убедитесь что файл доступен по HTTP/HTTPS
3. Проверьте настройки через "Получить Профиль Автозагрузки"
4. Запустите загрузку (помните об ограничении в 1 час)		 This notice property explains the manual file upload process linked to the user profile. The file must be accessible at the time of request and be in one of the supported formats (XLS, XLSX, CSV, XML). There is a strict rate limit of one request per hour; exceeding this will cause an API error. The upload ignores normal publication limits and publishes or activates all valid ads from the file, making it suitable for large catalog uploads. Users must configure the file URL in their profile beforehand, ensure HTTP/HTTPS accessibility, verify profile settings, and then run the upload respecting the hourly limit.

Output

The node outputs JSON data representing the result of the requested operation. For the "🚀 Ручная Загрузка Файла" operation under the "Автозагрузка" resource, the output JSON typically contains information about the success or failure of the file upload process, including any relevant status messages or errors returned by the Avito API.

If the operation encounters an error (e.g., due to rate limiting or file access issues), the output JSON will include an error field describing the problem.

No binary data output is indicated for this operation.

Dependencies

  • Requires an API key credential for authenticating with the Avito API.
  • The file to be uploaded must be accessible via HTTP or HTTPS at the URL configured in the user's profile.
  • The node depends on internal routing utilities to handle different resources and operations but these are abstracted away from the user.
  • No additional external dependencies beyond the Avito API and proper credential setup.

Troubleshooting

  • Rate Limit Errors: Since the API enforces a maximum of 1 request per hour for this operation, users may encounter errors if they exceed this limit. To resolve, schedule uploads accordingly and avoid multiple triggers within an hour.
  • File Accessibility Issues: If the file URL is incorrect, inaccessible, or the file format is unsupported, the upload will fail. Ensure the file is publicly accessible over HTTP/HTTPS and is in one of the supported formats (XLS, XLSX, CSV, XML).
  • API Authentication Failures: Incorrect or missing API credentials will prevent successful requests. Verify that the API key credential is correctly configured in n8n.
  • Unexpected Errors: The node returns error messages in the output JSON under the error field. Review these messages to identify issues such as malformed requests or server-side problems.

Links and References

Discussion