List of scopes
| Scope | What you get | What the member sees on the consent screen |
|---|---|---|
identity |
member number, username, display name, picture, verification badge | Your name, username and picture |
profile |
the public profile of the member and of other members: only fields visible on a public profile | Your public profile, as other members see it |
scores |
saving the member's scores to your app leaderboards | Saving your scores to this app leaderboards |
activity |
the “is playing …” indicator in chats while the member uses the app | Showing that you are using this app |
share |
the post window on the Network with your prepared text (only in a frame on BalkTalk) | Opening the post window on the Network - you send the post |
Rules
identityis the base of every sign-in. It is added even when you do not list it.- In the portal you declare the scopes your app may ask for. A request for a scope you have not declared is refused before the consent screen.
- Consent is remembered. The member sees the screen again only when you ask for a scope they have not granted yet.
- A public app that adds a scope in the portal waits for a new review. Until the decision it works with the old scopes.
- A call without the needed scope returns
403with"error": "insufficient_scope"and the scope name in thescopefield.
What no scope gives
- private messages and group messages
- e-mail address, password and sign-in details
- location and the Nearby module
- Upoznaj, profile verification, the Wallet and ducats
- posting, commenting or reacting in a member's name
- moderator or administrator powers, even when the member who signed in is a moderator
If you need something that is not here, write to us. The public API grows on purpose, one thing at a time.