OZON Seller

Integrate with OZON Seller API

Actions14

Overview

This node integrates with the OZON Seller API to update product prices on the OZON marketplace. Specifically, the Update Price operation under the Product resource allows users to send price updates for one or multiple products in bulk.

Typical use cases include:

  • Automatically adjusting product prices based on market conditions or inventory levels.
  • Synchronizing prices from an external system or database to OZON.
  • Applying promotional or discount pricing programmatically.

For example, a user might feed a list of product IDs and their new prices into this node to update all prices at once, ensuring the online store reflects current pricing strategies.

Properties

Name Meaning
Payload (JSON) Optional JSON payload that will be merged with the auto-generated price update payload. This allows adding or overriding fields in the request sent to OZON's API.

Output

The node outputs a single JSON object containing the response from the OZON API after attempting to update product prices. The structure typically includes success indicators, error messages if any, and details about the updated prices.

Example output JSON structure (simplified):

{
  "result": {
    "updated": [...],   // List of successfully updated price entries
    "errors": [...]     // Any errors encountered during update
  }
}

No binary data is produced by this node.

Dependencies

  • Requires an API key credential for authenticating with the OZON Seller API.
  • Uses HTTP POST requests to OZON endpoints.
  • Supports optional configuration for base URL override and timeout settings.
  • Handles automatic retries on rate limiting or server errors (up to 3 retries 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 data) are surfaced with messages including HTTP status codes. Verify credentials and payload correctness.
  • Rate Limiting: The node automatically retries on HTTP 429 responses, but excessive requests may still cause failures. Consider reducing request frequency.
  • Timeouts: Network timeouts can occur; adjust timeout settings if necessary.

Links and References

Discussion