Glizer/OpenAPI: Unterschied zwischen den Versionen
Krim (Diskussion | Beiträge) (→Important Information) |
Krim (Diskussion | Beiträge) (→Note Details) |
||
Zeile 11: | Zeile 11: | ||
==Note Details== | ==Note Details== | ||
* http://api.glizer.net/rpc.php?api=user | * http://api.glizer.net/rpc.php?api=user | ||
− | Valid parameters are: username=USERNAME or uuid=UUID (no separators like "-" should be used). Always prefer using UUID! | + | Valid parameters are: username=USERNAME or uuid=UUID (no separators like "-" should be used). Always prefer using UUID! The output is limited to 100 (newest) notes. |
====Output==== | ====Output==== | ||
This request will return an array of all avaiable reputations. Relevant informations are: | This request will return an array of all avaiable reputations. Relevant informations are: |
Version vom 1. März 2015, 19:21 Uhr
Details: Install | Commands | Permissions | Register | Callback | Stats | Prowl | Changelog | Ban System | Ban and Dispute rules | Terms of Usage | Compromised Account | Privacy | BungeeCord
Comparison: Comparison of glizer with MCBans
Download: Download
Inhaltsverzeichnis
OpenAPI
Glizer offers an open API for developers to implement a check against glizer from outside minecraft. All request result in an json encoded string. If possible: use HTTPS
Important Information
This API has a high security system. Please cache the results if you use them internally. If there are too many requests per minute the API will throttle down and eventually ban your client. If you have an API key you can add it as apikey=KEY to the request to reduce the chance to get banned
Note Details
Valid parameters are: username=USERNAME or uuid=UUID (no separators like "-" should be used). Always prefer using UUID! The output is limited to 100 (newest) notes.
Output
This request will return an array of all avaiable reputations. Relevant informations are:
- message - The ban reason
- given - timestamp of the ban
- fromuser - the person who banned the player, may be a server
- fglobal - binary 0/1 - flag for a global ban
- reputation - the requested reputation change. positive for praise, negative for warn, if <= -100 it's a ban, if >=100 it's an unban
- greputation_change - the change of the global reputation by this note
- reputation_change - the change of the local reputation by this note
- timelimit - if not 0: it's a timeban. timelimit are seconds. if given + timelimit > the actual timestamp: this note is active
- serverurl - the server on which this note has been reported
- servername - the servername ;-)
User Details
Valid parameters are: username=USERNAME or uuid=UUID (no separators like "-" should be used). Always prefer using UUID! Additionally it's possible to set serverid=SERVERID to change the selected server. Default server is the Glizer Master Server
Output
This request will return informations of a user. Relevant informations are:
- relation - reputation change of the user by related (sub)accounts of the user
- shared - reputation change by server banshares
- localglobal - mixed reputation on the selected server
- global - the global reputation of the user on glizer
- local - the local reputation on the selected server
- templocal - the local reputation resulted by temporary notes
- banned - boolean (true/false) can this user access the server
- servers - subarray - contains "Server","Last_Seen","Online_Time","Local_Reputation" of servers, which added a note on this user