Minecraft compatibility

WebcraftAPI version 3.0.0 :

• 1.20.1 - Tested - OK
• 1.20.2 - Tested - OK

WebCraftAPI version 2.1.0 and below :

• 1.18 - Tested - OK
  
• 1.18.1 - Tested - OK
  
• 1.18.2 - Tested - OK
  
• 1.19 - Tested - OK
  
• 1.19.1 - Tested - OK
  
• 1.19.2 - Tested - OK
• 1.19.3 - Tested - OK
• 1.20.1 - Bug with the plugin folder -> Update to 3.0.0
• 1.20.2 - Bug with the plugin folder -> Update to 3.0.0

Links

[NEW] WebCraftAPI Documentation (all versions) : https://doc.webcraftapi.fr/

WebCraftAPI Dashboard for v3.0.0 : https://dashboard.webcraftapi.fr/

[NEW] - Configuration generator (beta) for v2.x.0 : https://depatin-florian.fr/WebCraftAPI/tools/config_generator/index.php?version=2.0.0

What is WebCraftAPI ?

WebCraftAPI is a simple, lightweight, highly configurable and secured REST API for Spigot servers. It allows for server admins/developpers to query and interact with their servers using simple REST semantics.
This plugin can also be used to integrate your server data into your website, application, or anything that speaks HTTP, as long as you know how to query an API. This means that you can create whatever you want from the data you get from the server, like real time monitoring applications, online/offline players list, player localization, alert system when the server goes offline, your imagination is the limit !


What kind of data can I query ?

You can query data about :

• Banned Players / IPs
• Server OPs
• Ping
• Players data (Name, position, online/offline, health, last time played...)
  
• Plugins (Plugin list, version, enabled ...)
  
• Server (Server version, minecraft version, is the server online ...)
  
• API Version (Author, version, description ...)
  
• Whitelist (Enabled, whitelisted players)
• Worlds (Name, time, spawn position, pvp enabled, difficutly ...)

What about endpoints security ?

As this plugin is accessible frow the web, I put some effort trying to securize it as much as I can, without making it too hard to use.

For now, there is 4 ways to securize it, so everyone can find the solution
that suits him best :

• Open authentication (not recommended, all data available)
• Basic authentication using login/password (allows only one user, all data available)
• Basic API key authentication (Multiple shared keys, allows multiple users, all data available)
• Advanced API key authentication (Multiple shared keys, allows multiple users, public/protected/admin keys for public/protected/admin data)