Application permission capabilities

Each application has its own certificate permissions. The permissions determine the APIs that the application can call and the APIs that can be applied for. After the application application is successful, you can view it directly on the Open Platform Console-Application Management-Overview "APP Certificate" page, as shown below. At the same time, the interfaces that each application can apply for are also on this page. If it is displayed on this page, it means that the current application of this interface can apply. If it is not displayed, it cannot apply.

#API

Permission Attribution

Each API has its own permission group and application. This requires that to obtain an API permission, you must find the permission group to which it belongs. and corresponding application types. In the API document, you can see the permission group to which each API belongs. If you need to obtain the API permissions of

taobao.itemprops.get, then you can know which types of applications you need to apply for to obtain permissions from the description at the bottom of the api document page.

##

Other related instructions

Still taking the taobao.itemprops.get API as an example, the API also has "￥Basic" "No Authorization required" and other words (picture below).

"￥Basic" This sign indicates that calling the API requires a fee. Click directly to see the specific charging rules; if it is "￥Free", it means that calling the API There is no charge for the api.

"No authorization required" means that calling the api to obtain data does not require seller authorization. Specific to the api, that is, when calling the api, there is no need to pass the system parameter session (i.e. access_token); If the sign here is "Requires authorization", you need to obtain the seller's authorization before calling (authorization details click here)

##FAQ

There is no FAQ about this document