Content
Introduction
In order to make calls to some internal APIs, you’ll require an internal token generated through SSO.
This token allows you to verify your identity, and use any edge system managed through SSO via API, and it is not intended for external use. The permissions of the token are the same of the requesting user.
Tokens can be generated for both Staging or Production environments.
Table of Contents
Generating an Internal Token
Navigate to SSO Admin. On the bottom left side, click your name and select “ Profile ”
Click “ Generate New Token ”
A new personal token will be generated. Clicking over it will copy it, and you’ll be able to use it in any internal API that requires it.
Note :
The newly generated token remains visible until the page is reloaded. In case of losing the personal token, you can regenerate your token anytime, but keep in mind that the old token becomes inactive after regeneration or after clicking the button [Terminate all sessions].
The Staging token is only valid for Staging environments. To generate a Production token, navigate to SSO Production.
Using your Personal Token
Your personal token can be used to authenticate in any edge system managed through SSO that supports SSO personal tokens. You can still use the Game Server token for systems such as Level Editor.
Below you’ll find an example of the Internal Localisation API:
Fetch existing localisations:
Endpoint: /api/internal/localisations
Example request:
curl -X 'GET' \
'https://localisations-server-staging.tripledotapi.com/api/internal/localisations?app_id=app_id_of_your_game' \
-H 'accept: text/csv' \
-H 'X-Authorization: your_personal_token'
Response:
Key,Type,Desc,en,es
test_key,text,some description,hello,hola
If no valid token has been provided, the API will return an error (401):
{
"message": "Invalid access token",
"code": 1000
}
If no token is provided at all, the API will return a different error (400):
{
"message": "No token provided",
"code": 1020
}
Chunks 1
**Introduction**
In order to make calls to some internal APIs, you’ll require an internal token generated through SSO.
This token allows you to verify your identity, and use any edge system managed through SSO via API, and it is not intended for external use. The permissions of the token are the same of the requesting user.
Tokens can be generated for both Staging or Production environments.
**Table of Contents**
* * *
## Generating an Internal Token
1. Navigate to SSO Admin. On the bottom left side, click your name and select “ **Profile** ”
2. Click “ **Generate New Token** ”
3. A new personal token will be generated. Clicking over it will copy it, and you’ll be able to use it in any internal API that requires it.
**Note** :
- The newly generated token remains visible until the page is reloaded. In case of losing the personal token, you can regenerate your token anytime, but keep in mind that the old token becomes inactive after regeneration or after clicking the button **[Terminate all sessions]**.
- The Staging token is only valid for Staging environments. To generate a Production token, navigate to [SSO Production](https://sso.tripledotapi.com/admin).
## Using your Personal Token
Your personal token can be used to authenticate in any edge system managed through SSO that supports SSO personal tokens. You can still use the Game Server token for systems such as Level Editor.
Below you’ll find an example of the Internal Localisation API:
**Fetch existing localisations:**
**Endpoint:** `/api/internal/localisations`
_Example request:_
curl -X 'GET' \
'https://localisations-server-staging.tripledotapi.com/api/internal/localisations?app_id=app_id_of_your_game' \
-H 'accept: text/csv' \
-H 'X-Authorization: your_personal_token'
_Response:_
Key,Type,Desc,en,es
test_key,text,some description,hello,hola
If no valid token has been provided, the API will return an error (401):
{
"message": "Invalid access token",
"code": 1000
}
If no token is provided at all, the API will return a different error (400):
{
"message": "No token provided",
"code": 1020
}