More Service is operating normally

Migration Guide

Authentication API

POST /api/en/v1.0/authentication/token/new

V2 Documentation

In the first version of the API you needed to access our services using a token. We use the same mechanism in v2.

Version 1 API call:

Response


{
"status": "success",
"data": "3b554aa9a29eac5bd6474b5956638296"
}
                          

In the new version of the API it’s done like this:

Version 2 API call:

Authenticate API V2

Response


{
"auth_token": "91490f85cf631a6969130b0a47f72cfd"

}
Parameters V1 Parameters V2
api_key api_key
login_id login_id
Response V1 Response V2
data auth_token

POST/api/en/v1.0/authentication/token/new

V2 documentation

While you can leave your token to expire, it is still best practise to logout when you are finished.

We have changed how the token handling works in the new version of the API. Previously the token formed part of the URL, but in v2 it is sent as a HTTP Header.

Version 1 API call:

Version 2 API call:

Response


{
"status": "success",
"message": "You have been successfully logged out",
}

In the new version of the API it’s done like this:

Version 2 API call:

Close Session

This will return an empty response with HTTP Status 200.

Parameters V1 Parameters V2
token token
Response V1 Response V2
data empty