AppID, Appkey, Appsecret, Accesstoken

app_id, App_key, App_secret, for the platform, you need to assign the appropriate permissions to your developer account:
1. app_id is used to mark your developer account, is your user ID, this ID in the database to add search, easy to quickly find
2 App_key and App_secret is a pair of accounts, the same app_id can correspond to multiple app_key+app_secret, so the platform can assign you different permissions, such as App_key1 + App_secect1 only read-only permissions However, App_key2+app_secret2 has read and write permissions. This allows you to put the appropriate permissions on different developers. Where the permissions of the configuration are directly associated with App_key, App_key also need to add database retrieval, easy to quickly find
3 As to why should have App_key + App_secret This paired appearance mechanism, because to encrypt, usually in the first verification (similar to the login scenario), you need to use App_key (mark the permissions to request what) + App_secret (password, that you really have this permission) to apply for a token, that is, we often use the Access_token, after the data request, directly provide Access_token can verify the permissions.

The above 3 points said a bit Doha, do not know to speak clearly no, by the way to say the simplified scenario:
1 Omit app_id, he defaults to each user has and only a set of permissions configured, so directly app_id = App_key, and then add a app_secret is enough.
2 omit app_id and App_key, equivalent to app_id = App_key = App_secret, usually used in the open interface, especially in many Map class API Use this mode, this mode, with the purpose of app_id is only to count a user The number of times the interface was called.

AppID: Unique identifier of the app Appkey: Public key (equivalent to account) Appsecret: Private key (equivalent to password)

Token: Tokens (expiration expires)

How to use

1. When requesting authorization from a third-party server, bring the Appkey and Appsecret (server side required)

2. Third-party server verifies that Appkey and Appsecret have no records in DB

3. If so, generate a string of unique strings (token tokens), return to the server, and return the server to the client

4. The next time the client requests sensitive data, bring the token

AppID, Appkey, Appsecret, Accesstoken