OAuth 2.0 Device Code Flow in Ozon Seller API: Safer Authorization for Desktop and Server ToolsBrief · digest for November 17
Brief≈ 1 min

OAuth 2.0 Device Code Flow in Ozon Seller API: Safer Authorization for Desktop and Server Tools

Ozon Seller API now supports authorization via OAuth 2.0 Device Code Flow (RFC 8628). As the SellerDen channel points out, this solves a long-standing security headache whenever you connect a local 1C plugin, warehouse WMS, POS terminal, or headless server script that doesn't have a built-in browser.

Previously, you had to hand those tools a permanent master Api-Key—essentially giving third-party software a spare key to your entire seller account. Now linking works like signing into a smart TV with a short code:

  • the app sends Ozon its client_id and requested permissions (scope—products, orders, or analytics) and receives a secret device_code plus a short user_code;
  • you open the verification link in a browser on your laptop or phone and enter that code inside your Ozon Seller account;
  • the integration polls the oauth/token endpoint and, once you approve, receives a temporary JWT access_token and refresh_token.

Your permanent Api-Key no longer sits inside third-party code, and if a warehouse PC is ever compromised, you can revoke that specific app's access in one click from your portal. There is no rush to rebuild working integrations—Api-Key lifetimes haven't changed (I covered recent technical deadlines in my Ozon Seller API updates breakdown). Just make sure you only confirm codes for software you recognize, and strictly from inside your own account.

Want a deep diveVotes help us choose what to break down in detail. This material has 0 votes.
Sources · 2