OZON Seller

Integrate with OZON Seller API

Actions14

Overview

This node integrates with the OZON Seller API to retrieve stock information from warehouses. Specifically, the "Warehouse" resource with the "Stocks" operation allows users to query current stock levels and related data for products stored in OZON warehouses.

Typical use cases include:

  • Synchronizing inventory levels between OZON and other sales channels or internal systems.
  • Monitoring warehouse stock availability to trigger reorder processes.
  • Generating reports on stock status for operational insights.

For example, a user might configure this node to fetch stock data daily and update their ERP system accordingly.

Properties

Name Meaning
Payload (JSON) Optional JSON payload that will be merged with the automatically generated request payload. This allows customization of the API request parameters beyond the default ones.

Output

The node outputs a JSON object containing the response from the OZON API's warehouse stock endpoint. The structure typically includes details about stock quantities, product identifiers, and warehouse information as returned by the API.

No binary data output is produced by this operation.

Example output JSON structure (simplified):

{
  "stocks": [
    {
      "product_id": 123456,
      "warehouse_id": 789,
      "stock": 100,
      "reserved": 10,
      "in_transit": 5
    },
    ...
  ]
}

Dependencies

  • Requires an API key credential for authenticating with the OZON Seller API.
  • The node uses HTTP POST requests to the OZON API endpoints.
  • Supports configuration of base URL override and timeout settings via credentials.
  • Handles automatic retries on rate limiting or server errors with exponential backoff.

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: Errors returned by the OZON API (e.g., authentication failure, invalid parameters) will be surfaced with messages including the HTTP status code and API error message.
  • Rate Limiting: The node automatically retries requests if rate limited (HTTP 429), but excessive calls may still cause failures. Reduce request frequency or increase retry limits if needed.
  • Timeouts: Network timeouts can occur; verify network connectivity and consider increasing the timeout setting in credentials if necessary.

Links and References

Discussion