Glizer/OpenAPI: Unterschied zwischen den Versionen

Aus Minecraft Gameserver Wiki
Wechseln zu: Navigation, Suche
(Die Seite wurde neu angelegt: „{{Glizer}} <div style="padding: 3.5px;"></div> <div style="{{Layout}}"> ==OpenAPI== Glizer offers an open API for developers to implement a check against gliz…“)
 
(Security)
Zeile 38: Zeile 38:
  
 
==Security==
 
==Security==
This API has a high security system. Please cache the results if you use it 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 should directly contact the normal glizer API to reduce the risk of a timeban.
+
This API has a high security system. Please cache the results if you use it 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
 
</div>
 
</div>
  
 
[[Category:glizer]]
 
[[Category:glizer]]

Version vom 1. März 2015, 18:57 Uhr

glizer

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

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.

Note Details

Valid parameters are: username=USERNAME or uuid=UUID (no separators like "-" should be used). Always prefer using UUID!

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

Security

This API has a high security system. Please cache the results if you use it 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