OZON Seller

Integrate with OZON Seller API

Actions14

Overview

This node integrates with the OZON Seller API to manage products, specifically allowing you to archive products in your OZON seller account. Archiving a product typically means marking it as inactive or removing it from active listings without deleting its data permanently.

Common scenarios where this node is beneficial include:

  • Automatically archiving products that are discontinued or out of stock.
  • Managing product lifecycle by programmatically controlling which products are visible on the marketplace.
  • Bulk archiving multiple products based on business rules or external triggers.

For example, you could use this node to archive a list of product IDs that you no longer want to sell, helping keep your online catalog clean and up-to-date.

Properties

Name Meaning
Payload (JSON) Optional JSON payload. If provided, it will be merged with the auto-generated payload. This allows adding or overriding fields in the request body sent to the OZON API for archiving products.

Output

The node outputs a JSON object containing the response from the OZON API after attempting to archive the specified products. The structure generally includes results or status information about the archive operation for each product ID submitted.

Example output JSON structure:

{
  "results": [
    {
      "product_id": 123456,
      "status": "archived",
      "message": "Product archived successfully"
    },
    ...
  ]
}

No binary data output is produced by this node.

Dependencies

  • Requires an API key credential for authenticating with the OZON Seller API.
  • The node uses the official OZON Seller API endpoints.
  • Network access to https://api-seller.ozon.ru or sandbox endpoint if configured.
  • Optional configuration for maximum retry attempts on failed requests.

Troubleshooting

  • Invalid JSON in Payload: If the optional Payload (JSON) property contains malformed JSON, the node will throw an error indicating invalid JSON. Ensure the JSON syntax is correct.
  • API Errors: The node surfaces errors returned by the OZON API, including HTTP errors and rate limiting. Common messages include request timeouts, unauthorized access (check API keys), or invalid product IDs.
  • Rate Limiting: The node implements retries with exponential backoff for HTTP 429 or server errors. If you encounter repeated failures, consider reducing request frequency or increasing retry settings.
  • Missing Product IDs: Ensure that the input data contains valid product_id fields; otherwise, the archive operation will fail.

Links and References

Discussion