Open Platform
  • 中文
  • EN
取消
en
  • 中文
  • EN
中文
EN
取消
  • Third-party Platform

    • # Common Permissions Set Troubleshooting Guide

    This paper mainly provides a solution to the problem of 48001, 61007 and 61003 of the third-party platform call interface, and helps you locate and solve the problem that the interface can not be called properly because of permissions. Other error codes and their causes are available for viewingGlobal error code。

    # 48001

    There are two main reasons for 48001 errors:

    1,fire Function is not authorized, please confirm Official Account message template/The Mini Program has obtained permission for this interface.

    Third-party platforms are just Official Account message template Or the Mini Program call interface if the Official Account message template Or the Mini Program itself has not yet acquired the capability of the interface (for example, some interfaces require certification to be completed in order to obtain, Some interfaces are only open to the account of the enterprise main body, etc., you can consult the corresponding interface documentation), and the third-party platform will not have the call permission of the interface (except for special interfaces).

    (2) When calling the interface, the token is passed wrong.

    • It is usually the access of the Mini Program_Token, access to Official Account message template_Tokens, third-party platformscomponent_access_TokenThird-party platforms.authorizer_access_TokenA mistake.

    • There is, for example, an interface is a Mini Program interface, and then passed the authorizer generated with the Official Account message template_access_Token

    3, if only open to the service provider to call the interface, there may also be 48001 Official Account message template/The Mini Program has not yet licensed the corresponding permission set to a third-party platform, and the solution refers to the solution in 61007 below.

    4, if the above two reasons are ruled out the problem has not been resolved, please go to the community -Service Provider AreaPost feedback processing.

    # 61007

    The main reasons for the 61007 error are: Official Account message template/The Mini Program has not yet authorized the corresponding permission set to the third-party platform

    1, how the service provider to verify the Official Account message template/Has the Mini Program granted the corresponding permission set to the third party platform?

    Can be accessed by calling theapi_get_authorizer_infoInterface query that returns the func_Does the info contain the corresponding permission id,

    2, how to query the interface called belongs to which permission set id?

    AccessiblePermission Set Dxplaination Document。

    3, if the above reasons have not been resolved, please go to the community-Service Provider AreaPost feedback processing.

    # 61003

    • Such as[Mini Program Login] Interface, when appid has not been authorized to the component_Appid, there will be 61003 error.
    • The service provider should keep a copy of the authorization account information (which can be accessed by callingapi_get_authorizer_infoInterface query), then you can know whether the appid passed by the calling interface is in the authorized account list.

    # 61009

    • Example: {"errcode":61009,"errmsg":"code is invalid rid:XXXXXXXX"}

    • Code is invalid, at this time, please carefully check the developer

    1, whether to use the code within the validity period

    1. Whether to use other account code (compared to calling API on behalf of An account is actually using B account code)

    3, the code is wrong (such as the need to use the authorization code in the API parameter explaination is actually used in the pre-authorization code)

    4, developers can interfacegetRidInfoSelf-check rid information

    # Other Considerations

    1, when the developer has made a permission modification to the third-party platform that has been released on the whole network, if it has not covered the status of the entire network, the permissions seen on the authorization page will still remain as the permissions of the current network.

    2, as long as the first time the whole network release (including the subsequent modification of the whole network release), the current user in use will never be affected, can be used normally.

    (3) Third-party platform to add a check set of permissions, after the revision of the audit and the release of the whole network, the newly authorized Official Account message template Or Mini Program authorization will increase the application of new permissions, the old user has been authorized, the old permissions are not affected, but the new permission set requires the old user to re-scan the code authorization before it takes effect. Same goes for deleting permission sets.

    4, with the passage of time, the platform may add more interface capabilities in the permission set, at this time, there is no need for third-party platforms to re-release the entire network, nor do users need to re-scan the code authorization, the default will take effect.

    1. Currently only supported Official Account message template Or the Mini Program cancels the authorization of the third-party platform, and does not support the third-party platform's initiative to cancel the authorization for the time being.