What you may do
const url = 'https://example.com/api/v1/me/permissions';const options = { method: 'GET', headers: {cookie: '__Host-shardkeep_session=<__Host-shardkeep_session>'}};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request GET \ --url https://example.com/api/v1/me/permissions \ --cookie __Host-shardkeep_session=<__Host-shardkeep_session>Your effective permissions, by scope, for deciding what to offer. An API token restricted to some permissions gets only those, and never acts as a global administrator. The API still checks every request.
Authorizations
Section titled “Authorizations”Responses
Section titled “Responses”Your effective permissions.
Effective permissions by scope. A permission is allowed on a server
when it is in global, under the server’s team, or under the server
itself; creating a server needs it in global or under the team. A
team or server lists only what global does not already hold. Node
permissions take effect only in global.
object
Acts as a global administrator, which allows everything.
object
object
Example
{ "global": [ "servers.read" ], "teams": [ { "permissions": [ "servers.read" ] } ], "servers": [ { "permissions": [ "servers.read" ] } ]}Not signed in, or the credentials are invalid.
An RFC 9457 problem with a machine-readable code.
object
Stable machine-readable error code.
Example
{ "type": "about:blank", "title": "Conflict", "status": 409, "code": "conflict"}Shardkeep is free software under the AGPL-3.0. Minecraft is a trademark of Mojang AB; Shardkeep is not affiliated with or endorsed by Mojang or Microsoft.