Minecraft Server Hosting API Documentation
An alpha overview of the Ametistos API used by the web control panel for authentication, servers, players, files, access, notifications and account data.
Ametistos API Status During Alpha
The application communicates with the versioned Ametistos API at https://api.ametistos.com/api/v1.
The contract is still evolving during alpha, so integrations should handle validation errors, unavailable
features and response changes. Do not expose access tokens in browser logs or public repositories.
Authentication and Account Endpoints
POST /auth/email/resend— resend an email confirmation code.POST /auth/email/confirm— confirm an account with the received code.POST /auth/password/forgot— request a password-reset code.POST /auth/password/reset— verify the code and set a new password.GET /auth/google— begin Google authentication.PATCH /users/password— update the authenticated user password.
Minecraft Server and Player Operations
Authenticated server routes expose creation and configuration, runtime status, console commands, files,
software, extensions and player information. Player statistics are available from
/servers/players/stats/:serverId. Console-style moderation commands are sent through
/servers/command/:serverIdusing a JSON command payload.
Notifications, Access and Promocodes
The control panel reads account notifications from /notifications/me. Server-access routes
list collaborators and modify their scoped permissions. Promocode routes activate a code and return the
authenticated user's previously used promotions and benefits.
API Integration Requirements
- Send the current bearer token only to the configured Ametistos API origin.
- Check for a valid token before loading protected account or server routes.
- Handle 401, 403, 404, validation and compatibility responses explicitly.
- Invalidate cached server data after mutations such as uploads, commands or resets.
- Fetch container statistics only while the Minecraft server status is online.