Support existing app upgrade and can get existing authorized shop's token

Dear developers

In order to help the exist app transfer to using Open API 2.0 as soon as possible, adding a new API v2.public.get_refresh_token_by_upgrade_code to respond the refresh_token by

upgrade_code, when your original type app upgraded then no need to disturb the authorized seller to authorize again.

The refresh_token can be used as the request parameter of RefreshAccessToken API to get the access_token and new refresh_token.

-How can I get the upgrade_code?

-How many times this upgrade_code can be used for one shop?

Upgrade_code can be used 3 times for each authorized shop.

-Does this upgrade_code can be used for all shops?

Only can be used for the authorized shops with this partner.

-What's the upgraded app type will be?

If your are an third-party-developer, your original type app will be upgraded to ERP type,

If you are a seller developer, your original type app will be upgraded to Seller-in-House type.

-Can the non-original type app using the upgrade_code to get the refresh_token?

Yes, they can.

尊敬的开发者

为了支持存量的app升级并尽快对接Open API 2.0接口，新增接口v2.public.get_refresh_token_by_upgrade_code支持通过upgrade_code获取refresh_token，从而无需使存量的授权卖家因为app升级而需要再次授权。

通过接口v2.public.get_refresh_token_by_upgrade_code拿到的refresh_token可以用于RefreshAccessToken的入参，从而拿到access_token与新的refresh_token.

-如何获得upgrade_code？

-upgrade_code针对一个店铺可以使用多少次？

针对每个授权状态的店铺可以使用三次。

-upgrade_code是否适用于所有店铺？

只适用于目前与该app存在授权关系的店铺。

-original type的app升级后的app类型是什么？

如果是第三方开发者的话，升级后的app类型为ERP；

如果是卖家开发者的话，升级后的app类型为Seller-in-House。

-非Original类型的app是否可以使用upgrade_code拿到refresh_token？

可以。