Mint a KVM console link
curl --request POST \
--url https://my.server.express/api/v1/dedicated/{id}/console \
--header 'Authorization: Bearer <token>'const options = {method: 'POST', headers: {Authorization: 'Bearer <token>'}};
fetch('https://my.server.express/api/v1/dedicated/{id}/console', 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}/console"
headers = {"Authorization": "Bearer <token>"}
response = requests.post(url, headers=headers)
print(response.text){
"success": true,
"data": {
"url": "/v1/dedicated/console/go/abc123"
}
}{
"success": false,
"error": "<string>"
}{
"success": false,
"error": "<string>"
}{
"success": false,
"error": "<string>"
}{
"success": false,
"error": "<string>"
}Dedicated
Mint a KVM console link
Returns a relative URL (/v1/dedicated/console/go/<ticket>) that’s good once, for 60 seconds. Open it against the
API base URL in a new tab; that GET starts the TenantOS session and redirects to it, so the session URL never appears
in JSON. Needs operate access and a manageable billing status (not PENDING or SUSPENDED). Writes an OPEN_CONSOLE audit
entry.
POST
/
v1
/
dedicated
/
{id}
/
console
Mint a KVM console link
curl --request POST \
--url https://my.server.express/api/v1/dedicated/{id}/console \
--header 'Authorization: Bearer <token>'const options = {method: 'POST', headers: {Authorization: 'Bearer <token>'}};
fetch('https://my.server.express/api/v1/dedicated/{id}/console', 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}/console"
headers = {"Authorization": "Bearer <token>"}
response = requests.post(url, headers=headers)
print(response.text){
"success": true,
"data": {
"url": "/v1/dedicated/console/go/abc123"
}
}{
"success": false,
"error": "<string>"
}{
"success": false,
"error": "<string>"
}{
"success": false,
"error": "<string>"
}{
"success": false,
"error": "<string>"
}Authorizations
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.