API Tokens

Create a separate API token for each tool or partner that uses Fleet. Choose which apps it can access and what it can do. For example, give a monitoring tool permission to read server status, logs and metrics, or let a partner restart servers for one app. You can manage tokens in the Console, through the API or with Fleet MCP.

1. Choose appsMinecraftRust
2. Choose permissionsView servicesRestart servicesStop services
3. Your API token•••• •••• ••••

Create an API Token

Create a token in the Console or through the API. API creation requires your Permanent API Token.

Open Settings > API Tokens in the Console and select New API token.

1. Give it a unique name, such as Minecraft monitoring.
2. Choose an expiration date, or select No expiration.
3. Choose All apps or Only selected apps. All apps includes apps you create later.
4. Select the permissions the token needs. All permissions are selected initially; use Deselect all to start with an empty selection. Expand a category to choose individual actions.
5. Select Generate API token and copy the value into your integration.

You can show and copy the value again from the token list. Open a token's details to check its permissions, app access and expiration date.

Choose Apps and Permissions

App access defines where a token can act. Permissions, called abilities in the API, define what it can do.

To let a partner inspect and restart Minecraft servers, select Minecraft, then View and Restart under Services. Start and Stop remain unselected. Selecting a category selects all its actions; Update also includes View.

Account-wide permissions, such as registry access, apply across your entire account. Read and metadata responses can include saved credentials and secret-file contents.

Use a Token with the API

Send the token in the Authorization header:

Authorization: Bearer <API_TOKEN>

You can also list your tokens, show a token's value and revoke a token through the API. These token-management calls require your Permanent API Token.

Pass a Token to a Server

In your Server Config, open Environment Variables, select Add dynamic and enter a name such as ODIN_API_TOKEN. Choose System as the type, then select API Token and your token's name from the value menu.

You can set the same variables through the API when you create a Server Config or update one.

Fleet fills in the value when the server starts. Replace expired or revoked tokens in your Server Config before starting new servers.

Revoke or Replace a Token

Select Revoke beside a token and confirm. Requests using it stop working immediately; other tokens keep working.

To change a token's permissions, apps or expiry, create a replacement, update your integration and revoke the old token. The list shows your token usage and limit. Expired tokens still count until you revoke them.

Your Permanent API Token has full access and no expiration. You can show, copy or rotate it, but cannot delete it. Rotating it invalidates the previous value. Replace copied values and redeploy servers that receive it dynamically.