The usual cause is your Uzum API key
If your data in MyProfit stopped updating entirely (not just lagging by an hour), the usual cause is that your Uzum API key stopped working. MyProfit reads your data from Uzum with this key — without a working key, sync doesn’t run. The MyProfit interface is in Russian, so on-screen labels are shown here in quotes.
When this happens, MyProfit shows a banner in the header:
«Требуется ключ Uzum API. Для синхронизации данных с Uzum необходим ключ API. Обновите его в настройках.» (An Uzum API key is required. Refresh it in settings.)
In the banner, «Обновите его в настройках» is a clickable link: it opens the API-key section in Settings directly.
You can dismiss the banner for the current session, but it returns until the key is fixed. It also appears when just one of several connected shops loses key coverage — even if the rest still work.
How to fix it
- Open Settings («Настройки») → Uzum API («Uzum API»).
- Paste a fresh key into the API key field («Ключ API»).
- Click Save («Сохранить»).
On save, MyProfit checks the key against Uzum. If the key is valid, the warning clears, the message «Ключ сохранён» (Key saved) appears, and your shop list refreshes.
If the key isn’t accepted, saving in Settings shows a message that the key was rejected: «Ключ не принят Uzum. Проверьте корректность и попробуйте снова.» (Uzum did not accept the key. Check that it’s correct and try again.) In that case, create a fresh key in the Uzum cabinet and re-paste it.
The key works separately from your login
An API key can stop working even while you can still log in to the Uzum cabinet — it is separate from your login. MyProfit can’t tell expiry from revocation: either way, the fix is the same — create a new key in the Uzum cabinet and re-paste it. For how to create the key, see connect your Uzum shop.
Why a key may not be accepted
When you enter a key at registration, MyProfit may show a more specific reason:
- «Ключ недействителен или истек.» (Key is invalid or expired.) — the key is wrong or no longer valid; create a new one in the Uzum cabinet.
- «У ключа API нет доступных магазинов на Uzum.» (The API key has no available shops on Uzum.) — the key covers no shop; check it was created under the right account with shop rights.
- «Не удалось проверить ключ API. Повторите попытку через минуту.» (Could not verify the API key. Try again in a minute.) — a temporary check hiccup; wait a minute and try again.
When you save in Settings the message is more general — «Ключ не принят Uzum. Проверьте корректность и попробуйте снова.» (Uzum did not accept the key. Check that it’s correct and try again.); the fix is the same: create a fresh key in the Uzum cabinet and re-paste it.
If it’s not the key
If the key is fine but the data still looks incomplete, it may simply be sync lag — data updates on a schedule and is minutes to hours behind. See how data syncs and how fresh it is.