OZON Seller

Integrate with OZON Seller API

Actions14

Overview

This node integrates with the OZON Seller API to perform various operations related to orders, products, warehouses, and reports. Specifically, for the Order (FBBS) - List operation, it retrieves a list of fulfillment-by-seller (FBS) orders from the OZON marketplace.

Common scenarios where this node is beneficial include:

  • Fetching recent or filtered order data for processing or analysis.
  • Automating order management workflows by retrieving order details programmatically.
  • Integrating OZON order data into other systems such as CRMs, ERPs, or custom dashboards.

For example, a user can configure this node to pull all new FBS orders placed within a certain date range, then use subsequent nodes to update inventory or notify shipping teams.

Properties

Name Meaning
Payload (JSON) Optional JSON payload that will be merged with the auto-generated request payload for listing orders. This allows customizing filters or parameters sent to the OZON API.

Output

The node outputs a single JSON object containing the response from the OZON API's order listing endpoint. The structure typically includes order details such as order IDs, statuses, customer information, and shipment data.

Example output structure (simplified):

{
  "result": [
    {
      "posting_number": "123456789",
      "order_id": 987654321,
      "status": "awaiting_packaging",
      "items": [...],
      "customer": {...},
      ...
    },
    ...
  ],
  "total": 100,
  "limit": 50,
  "offset": 0
}

No binary data is produced by this operation.

Dependencies

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

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) are surfaced with messages including HTTP status codes. Verify API credentials and request parameters.
  • Rate Limiting: The node automatically retries requests when receiving rate limit responses but excessive calls may still cause delays or failures. Consider adjusting usage frequency.
  • Timeouts: Network timeouts can occur; increasing the timeout setting in credentials may help if large datasets are requested.

Links and References

Discussion