OZON Seller

Integrate with OZON Seller API

Actions14

Overview

This node integrates with the OZON Seller API to retrieve commission reports. Specifically, when using the Report resource with the Commissions operation, it fetches commission-related data from the seller's OZON account.

Typical use cases include:

  • Automating the retrieval of commission reports for accounting or financial reconciliation.
  • Integrating commission data into dashboards or other business intelligence tools.
  • Combining commission data with other sales or finance reports for comprehensive analysis.

For example, a user might schedule this node to run daily to collect updated commission information and then push that data into a spreadsheet or database for further processing.

Properties

Name Meaning
Payload (JSON) Optional JSON payload string. If provided, it will be parsed and merged with the auto-generated request payload sent to the OZON API. This allows customizing or extending the default request parameters.

Output

The node outputs a single item containing a json field with the commission report data returned by the OZON API. The structure of this JSON depends on the API response but generally includes details about commissions related to sales activities.

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.
  • Network access to the OZON API service must be available.
  • Optional: The user can provide additional JSON payload data to customize the API request.

Troubleshooting

  • Invalid JSON in Payload: If the "Payload (JSON)" property contains malformed JSON, the node will throw an error indicating invalid JSON. Ensure the JSON syntax is correct before running the node.
  • API Request Errors: Errors from the OZON API (e.g., authentication failures, rate limits, server errors) will be surfaced with messages including HTTP status codes and API error messages. Check API credentials and network connectivity.
  • Rate Limiting: The node implements retry logic for HTTP 429 (Too Many Requests) and server errors, but excessive requests may still cause failures. Reduce request frequency if encountering repeated rate limit errors.
  • Empty or Unexpected Response: Verify that the input data and optional payload are correctly structured and that the account has commission data available for the requested period.

Links and References

Discussion