# Marketplaces and Avito Every marketplace connects under **Integrations**, on the **Services** tab. The general rules (kinds of connection, statuses, Read-only, disconnecting) are in [Connecting services](/help/integrations), safe price and stock edits in [Approving actions](/help/trust). This page covers what each marketplace does its own way. Work scenarios for each marketplace are in the [marketplaces catalog](/integrations/marketplaces). | Marketplace | How it connects | What to paste | |---|---|---| | Ozon | Sign in through Ozon or a Seller API key | Nothing, or Client ID and API Key | | Wildberries | A token from WB Partners | API Token | | Yandex Market | A Yandex confirmation code or an API key | Nothing, or API Key | | Avito | Keys from the Integrations section on Avito | Client ID and Client Secret | | Megamarket, Kaspi.kz, Uzum Market | A token from the seller account | API Token | ## Ozon Ozon Seller API: the seller's products, orders, stock, prices, chats, reviews and analytics. [Integration page](/integrations/ozon). ### What the agent can do Reads products, orders, stock and analytics, replies in chats and to reviews, changes prices, discounts and stock, works with supplies. Accruals and financial reports are available only with a key that has the Finance role. Ozon notifications (new shipments, cancellations, chat messages) turn on by themselves at connection, and [tasks](/help/tasks) can run on them. ### Before you start Access to seller.ozon.ru with the Administrator or Manager role. Ozon has two ways to connect in one window: the **Connect via Ozon** button and the line under it, **Another way to connect: Ozon Seller API (API key)**. | | Sign in through Ozon | Seller API key | |---|---|---| | Permissions | Ozon's set for apps: products, orders, stock, chats, reviews, discounts, supplies | The roles you ticked when issuing the key | | Finance (accruals, financial reports) | No | Yes, with the Finance role | | One seller account from two places (a colleague, another organization) | No: Ozon keeps one such connection per account | Yes | ### Steps Sign in through Ozon: ### Sign in to seller.ozon.ru with the right role Only an Administrator or a Manager can grant access to an app. Other roles never see Ozon's consent screen. ### Pick the company If your account holds several shops, Ozon asks you to pick a company: access goes to one seller account. ### Check the permissions and click Allow The agent gets full access, chats, discounts and supplies included. You can keep it read-only later on the connection card, under Changes. A key with the Finance role: ### Open the key form Under Integrations open Ozon and, below Connect via Ozon, click **Ozon Seller API (API key)**. A form opens with the **Client ID** and **API Key** fields. ### Issue the key in Ozon On seller.ozon.ru open Settings, then API keys, as an Administrator or Manager and create a key with the roles you need. ### Copy both values right away Ozon shows the key once. Paste Client-Id into Client ID and Api-Key into API Key, and only then close the Ozon window. ### Permissions to grant Accruals and financial reports need the **Finance** role. The connection accepts a key with any role, but the agent sees only what the ticked roles open. Ad campaign statistics come from a separate advertising API: that is the **Ozon Performance API** tile, described below. ### Limitations If this seller account is already connected through Ozon sign-in by a colleague or in another organization, that connection stops working and shows **Access held by another connection**. To work with the account from two places, connect it with a key. ### How to revoke access - **Ozon sign-in**: Settings, then Apps and permissions in the Ozon account. - **Seller API key**: delete the key under Settings, then API keys. **Disconnect** on our side removes only our connection; access in the Ozon account stays after it. ### Troubleshooting - **No financial data**: the connection was made with Ozon sign-in or with a key without the Finance role. Connect a key with that role through Add another. - **Notifications do not arrive**: if another integration, a CRM for instance, already receives them, the address does not change until you click **Replace address**. ## Ozon Performance API The Ozon advertising account (Performance API): campaigns, statistics, bids and promotion. A separate tile in the catalog with its own keys. ### What the agent can do Reads campaigns and their statistics, changes bids and promotion settings. ### Steps ### Open Performance API In the Ozon Seller account: Settings, then Performance API. ### Pick or create a service account To keep apps' access apart, create a separate service account. ### Add a key and paste it In the service account click Add key. Paste the values into **Advertising account Client ID** and **Client Secret**. ### Limitations Roles are not chosen for an advertising key. A Seller API key does not work here, and the other way round. ### How to revoke access Delete the key in the Performance API service account and click Disconnect on the Ozon Performance API card. ### Troubleshooting **Credentials not accepted**: check that you pasted the Performance API service account keys, not Seller API keys. ## Wildberries Wildberries API: the seller's products, orders, prices, stock, ads, reviews and finance. [Integration page](/integrations/wildberries). ### What the agent can do Computes sales, stock on your own and WB warehouses, unit economics and ad spend, replies to reviews and questions, writes to a buyer in chat, changes prices. Wildberries does not push events to third-party services, so new reviews, questions and orders are checked by a [scheduled task](/help/tasks). ### Before you start The account owner's sign-in at seller.wildberries.ru: only the owner issues and deletes API tokens, other roles do not see the section. There is no need to look for our service in the WB solutions catalogue: WB issues a Service token only to services from that catalogue, and we need a Base one. ### Steps ### Open API access Hover over the seller name in the top-right corner: Settings, then API access, then Create new token. ### Create a Base token On the Manual integration tab give it a name and pick the **Base** type. ### Tick the ten categories and Read and write The categories and what each is for are in the table below. ### Copy the token and paste it The token is shown once. Paste it into the **API Token** field on the Wildberries card. The token string starts with eyJ. ### Permissions to grant The connection accepts a token only with all ten categories. Wildberries does not let you add a category to an issued token, only issue a new one, so the missing ones are named at connection rather than in the middle of a task. | Category | What the agent needs it for | |---|---| | Content | product listings, photos and videos | | Analytics | sales funnel, listing and stock reports | | Prices and discounts | reading and changing prices, discounts, promotions | | Marketplace | assembly orders, your own warehouses and their stock | | Statistics | sales, orders and stock at WB warehouses | | Promotion | ad campaigns, bids, spend | | Questions and reviews | replies to buyers, pinning reviews | | Buyer chat | messages with a buyer | | Buyer returns | return claims | | Finance | the sales report: commissions, logistics, storage, payouts | Recommendations, Supplies and Documents are not needed by the connection. **Read and write** access is needed for replies, prices and bids. If the token is issued read-only, the agent only reads and answers a change request by saying a token with write access is needed. ### Limitations Wildberries limits the token's lifetime. When it expires, the connection shows **Credentials not accepted**. ### How to revoke access Delete the token in the same API access section and click Disconnect on the Wildberries card. ### Troubleshooting - **The token is refused at connection**: the refusal names the missing categories. Issue a new token with all ten. - **Credentials not accepted** on a connection that worked: the token expired or was deleted. Issue a new one and click **Re-enter credentials**. ## Yandex Market The seller's campaigns, orders, products, prices and stock. [Integration page](/integrations/yandex-market). ### What the agent can do Works with products, prices, stock and orders of the shops the connected login can reach, and with Market events through notifications. ### Before you start A Yandex login that will stay with the business for a long time: access is granted to the login, not to the account, and changing its password or two-factor setup, or recovering the login, resets the access. ### Steps ### Invite the login to the account and give it a role The owner invites the login on partner.market.yandex.ru and assigns a role for each shop. ### Connect Click **Connect**, then **Copy the code and open**, enter the code on the Yandex page with that login and come back: the connection picks up on its own. ### Pick the account If the login sees several accounts, pick a **Yandex Market business** and click **Connect business**. ### Turn on notifications Copy the **Webhook address** from the connection card. In the Market account click the account name, then Settings, API and modules, API notifications, Connect notifications; paste the address, tick the events you need and save. If Yandex sign-in did not work, the same window has **Yandex Market (API key)**: on partner.market.yandex.ru open Settings, then API and modules, issue a static Partner API key for the businesses and shops you need and paste it into the API Key field. ### Permissions to grant The API and modules section is visible to the Account administrator, Account manager, Shop administrator, Developer and Operator roles; the Content manager does not see it. Chat events in notifications can be turned on only by the account owner or manager. ### Limitations The agent sees only the shops the login can reach. Market notifications do not turn on by themselves; they are connected in the Market account. ### How to revoke access Remove the login from the account on partner.market.yandex.ru or delete the static key in API and modules, then click Disconnect on the card. ### Troubleshooting - **The connection stopped working after the login's password changed**: sign in again with **Reconnect**. - **No events**: check that the webhook address is pasted into API notifications in full and the events you need are ticked. ## Avito Listings, statistics, messenger, reviews and autoload. [Integration page](/integrations/avito). The advertising account connects as a separate Avito Ads tile, described in [Ads](/help/ads). ### What the agent can do Reads listings and statistics, replies to customers in the Avito messenger, works with reviews. Events come through the webhook: new message, new chat, new review, review updated. Customers get replies from a task that runs on an event. In the task form pick the **On event** trigger, **Service** Avito, **Event type** "new message", and in the **Result** row tick **Reply to the other party**. In the task text say what to answer right away, what to pass to you and what not to promise. To turn replies off, open the task and click **Pause** or delete it. ### Before you start A paid Avito plan on the account that holds the listings: Avito issues personal keys only to such accounts. ### Steps ### Open the integrations section on Avito Profile management, then Settings, then Integrations, or go straight to avito.ru/professionals/api. ### Click Get keys Client ID and Client secret appear. If the area is empty, reload the page after a minute: keys are not created instantly. ### Paste both strings Client ID into **Client ID**, Client secret into **Client Secret**. The Avito webhook registers itself at connection. ### Limitations Keys work only for the account where they were issued: a second account connects with its own keys. The task's reply is not instant: each new message starts the task, and the reply goes out when the agent finishes. Several messages from one customer in a row end up in one reply, messages from different customers are handled in parallel. Reviews cannot be answered this way: Reply to the other party is available only for chat events. ### How to revoke access Click Disconnect on the Avito card. The keys are issued in the Integrations section of the Avito profile; check and change them there. ### Troubleshooting - **Not receiving messages**: the webhook registration on Avito failed. Click **Check again**. If the status then changes to **Credentials not accepted**, check the keys on Avito and enter them again. - **Used by another service**: the account's messages already go to another integration. **Replace address** takes them over, and the other integration stops receiving them. ## Megamarket Products, orders, stock, prices, FBO supplies, DBS delivery and reports. [Integration page](/integrations/megamarket). ### Before you start An account with administrator rights in partner.megamarket.ru: a user with reduced rights does not see the API section. ### Steps ### Open API integration On partner.megamarket.ru: Settings, then API integration. ### Copy the authorization token Take the token of the account's production environment and paste it into the **API Token** field. ### Limitations If there is no API integration item, the account works under FBO without the API or lacks rights: Megamarket support turns access on in chat. ### How to revoke access Click Disconnect on the card. The token is issued on the API integration page of the Megamarket account; check and change it there. ### Troubleshooting **Credentials not accepted**: the test and production environments have different tokens, and a test token is not accepted on production requests. ## Kaspi.kz Kazakhstan: orders, products, reviews, cities and pickup points. [Integration page](/integrations/kaspi). ### Before you start The company head's account in the kaspi.kz/mc web account: the token is issued only to the head, and the mobile app has no token section. ### Steps ### Open API token In the kaspi.kz/mc account: Settings, then API token. ### Click Generate and copy it Paste the token into the **API Token** field. ### How to revoke access Click Disconnect on the card. The token is issued on the API token page of the Kaspi account; check and change it there. ### Troubleshooting **There is no API token item**: you signed in as an employee rather than the head. Ask the head to issue the token. ## Uzum Market Uzum Market Seller API: the seller's products, orders, stock and finance. [Integration page](/integrations/uzum-market). ### Before you start The account on seller.uzum.uz the shop is registered to, with rights to the settings, and an active shop. ### Steps ### Issue a Seller API token In the profile settings open the API and integrations section and issue a token. ### Copy the token right away Paste the string into the **API Token** field without the word Bearer and without spaces at the ends. A previous token cannot be recovered. ### How to revoke access Click Disconnect on the card and revoke the token in the API and integrations section of the Uzum profile. ### Troubleshooting **The agent sees no orders**: without an active shop the account's list of shops is empty. ## Several shops and accounts Each shop or account connects separately: open the connected marketplace and click **Add another**. - **Ozon**: with Ozon sign-in pick another company, or paste a key from the second shop's account. - **Wildberries**: the token is issued in each seller's account. - **Yandex Market**: one login can see several accounts; then the card has a **Default account** row, and the agent takes another account when you name it in the request. - **Avito**: a second account connects with its own keys. Name the shop in words in the request: "for the Main account on Ozon". One scheduled task per account: this way each has its own run history, more in [Tasks](/help/tasks).