OZON Seller

Integrate with OZON Seller API

Actions14

Overview

This node integrates with the OZON Seller API to interact with warehouse-related data, specifically focusing on Acceptance Acts in this context. It allows users to retrieve lists of acceptance acts from their OZON warehouse, which are documents confirming the receipt and acceptance of goods into the warehouse.

Common scenarios where this node is beneficial include:

  • Automating inventory reconciliation by fetching acceptance act records.
  • Integrating warehouse receipt confirmations into broader supply chain workflows.
  • Auditing and tracking goods received at the warehouse for accounting or operational purposes.

For example, a user might use this node to periodically pull acceptance acts to update their internal ERP system with confirmed stock receipts.

Properties

Name Meaning
Payload (JSON) Optional JSON payload that will be merged with the auto-generated request payload. This allows customization or extension of the default query parameters sent to the API.

Output

The node outputs a JSON object containing the response from the OZON API endpoint for acceptance acts. The structure depends on the API's response but generally includes details about acceptance acts such as act IDs, dates, statuses, and related warehouse information.

No binary data output is produced by this operation.

Dependencies

  • Requires an API key credential for authenticating with the OZON Seller API.
  • The node uses the official OZON Seller API endpoints, either production or sandbox based on configuration.
  • Network connectivity to https://api-seller.ozon.ru or the sandbox URL is necessary.
  • The node supports automatic retries on rate limiting or server errors, configurable via credentials.

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 failures, invalid parameters) will be surfaced with messages including HTTP status codes. Verify API credentials and payload correctness.
  • Rate Limiting: The node automatically retries requests if rate limited (HTTP 429). If repeated failures occur, consider reducing request frequency or increasing retry settings.
  • Network Issues: Connectivity problems to the OZON API endpoints will cause request failures. Check network access and proxy/firewall settings.

Links and References

Discussion