Scopes and templates for access tokens

GET

/v1/tokens/scopes

const url = 'https://api.gampeon.com/v1/tokens/scopes';
const options = {method: 'GET'};

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://api.gampeon.com/v1/tokens/scopes

All scopes an access token can have, the templates the portal offers and the limits. Which route needs which scope is in x-gampeon-token-scope on each operation. Routes without it can never be used with an access token.

Responses

200

Scopes

application/json

object

scopes

required

Array<object>

object

name

required

Scope

string

Allowed values: profile:read projects:read projects:write marketplace:read marketplace:write servers:read

description

required

string

templates

required

Array<object>

object

required

string

title

required

string

scopes

required

Array<string>

Allowed values: profile:read projects:read projects:write marketplace:read marketplace:write servers:read

defaultExpiresInDays

required

integer

maxExpiresInDays

required

integer

maxActiveTokens

required

integer

Example

{
  "scopes": [
    {
      "name": "profile:read"
    }
  ],
  "templates": [
    {
      "scopes": [
        "profile:read"
      ]
    }
  ]
}

Report a problem with this page Other ways to give feedback