Wildberries and Ozon API integration

Who it is for

An API integration pays off when photos change often and in volume. With a few dozen cards, manual upload in the seller account is fine. With hundreds or thousands, manual work becomes the bottleneck.

• Sellers with hundreds of cards on Wildberries and Ozon
• Brands selling the same products on both marketplaces
• Agencies and studios managing several client accounts
• Marketplace managers responsible for card content

What Solistra reads

Reading is needed to find a card and keep its current photos. Solistra requests cards and their images by seller SKU, nmID for Wildberries, or offer_id and SKU for Ozon. Nothing else in the store is read.

Every connection in the Integrations section lists what Solistra may do: find cards by SKU, upload photos to cards and download photos from cards.

What Solistra writes

The only thing Solistra writes to a card is the final photo list. Prices, stock, descriptions, attributes, card videos and orders are never changed.

For Wildberries the photo list goes through the Content API methods, for Ozon through the product image import by link. Photos are served as permanent HTTPS links from storage in Russia, with EXIF stripped and an unguessable address.

Which permissions to grant

The rule is simple: the key grants exactly what photos need. The Wildberries help center notes that even if a token leaks, access is limited to the data categories you selected.

Where keys are stored

Keys are encrypted and stored only on a server in Russia. They never reach the browser, logs or Solistra API responses. Requests to Wildberries and Ozon go directly from Russia with no foreign gateway.

Disconnecting an account in Solistra deletes the key. You can also revoke the token or key in the seller account at any time and access stops immediately.

Rate limits and retries

Both the Wildberries and Ozon APIs limit how often you can call them. Solistra queues uploads, respects those limits and runs one active batch per account.

If the marketplace says there are too many requests or returns a temporary server error, Solistra waits and retries. If the outcome of a write is unclear, there is no blind second write: Solistra reads the card first and checks what is already there.

Read back and history

After every write Solistra reads the card back and compares the photos with the list it sent. Success is not shown until that check passes.

Before writing, the previous photo set is saved as a snapshot in the log. The log shows uploads, downloads, key checks, errors and rollbacks, and any snapshot can be restored to the card in one click.

How to connect

Setup takes a few minutes and needs no developer.

• Create a WB token with the Content category or an Ozon key with a product role
• Open Integrations in Solistra and pick the marketplace
• Paste the key and click Check
• Review the list of permissions for the connection
• Go to Cards and send your first series