Reveal the server's root password
curl --request GET \
--url https://my.server.express/api/v1/dedicated/{id}/credentials \
--header 'Authorization: Bearer <token>'const options = {method: 'GET', headers: {Authorization: 'Bearer <token>'}};
fetch('https://my.server.express/api/v1/dedicated/{id}/credentials', options)
.then(res => res.json())
.then(res => console.log(res))
.catch(err => console.error(err));import requests
url = "https://my.server.express/api/v1/dedicated/{id}/credentials"
headers = {"Authorization": "Bearer <token>"}
response = requests.get(url, headers=headers)
print(response.text){
"success": true,
"data": {
"username": "root",
"password": "<string>"
}
}{
"success": false,
"error": "<string>"
}{
"success": false,
"error": "<string>"
}{
"success": false,
"error": "<string>"
}{
"success": false,
"error": "<string>",
"data": {
"taskId": "<string>"
}
}{
"success": false,
"error": "<string>"
}Dedicated
Reveal the server's root password
The root (or Administrator, on Windows) password we set at order time or on the last reinstall. password is null
when we never set one. Needs operate access and a manageable billing status. Refused with 409 while a reinstall is
running, since the stored password belongs to the OS being wiped. Every reveal writes a CREDENTIALS_VIEW audit entry,
which shows on the activity tab.
GET
/
v1
/
dedicated
/
{id}
/
credentials
Reveal the server's root password
curl --request GET \
--url https://my.server.express/api/v1/dedicated/{id}/credentials \
--header 'Authorization: Bearer <token>'const options = {method: 'GET', headers: {Authorization: 'Bearer <token>'}};
fetch('https://my.server.express/api/v1/dedicated/{id}/credentials', options)
.then(res => res.json())
.then(res => console.log(res))
.catch(err => console.error(err));import requests
url = "https://my.server.express/api/v1/dedicated/{id}/credentials"
headers = {"Authorization": "Bearer <token>"}
response = requests.get(url, headers=headers)
print(response.text){
"success": true,
"data": {
"username": "root",
"password": "<string>"
}
}{
"success": false,
"error": "<string>"
}{
"success": false,
"error": "<string>"
}{
"success": false,
"error": "<string>"
}{
"success": false,
"error": "<string>",
"data": {
"taskId": "<string>"
}
}{
"success": false,
"error": "<string>"
}Authorizations
bearerAuthapiToken
Session access token (JWT) from POST /v1/auth/login or /v1/auth/refresh. A session satisfies every API scope.
Path Parameters
The dedicated server's service id.