List the BMC's IPMI accounts
curl --request GET \
--url https://my.server.express/api/v1/dedicated/{id}/ipmi \
--header 'Authorization: Bearer <token>'const options = {method: 'GET', headers: {Authorization: 'Bearer <token>'}};
fetch('https://my.server.express/api/v1/dedicated/{id}/ipmi', 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}/ipmi"
headers = {"Authorization": "Bearer <token>"}
response = requests.get(url, headers=headers)
print(response.text){
"success": true,
"data": {
"host": null,
"users": [
{
"id": 123,
"name": "<string>",
"privilege": "OPERATOR",
"enabled": true
}
],
"hasCustomerAccount": true
}
}{
"success": false,
"error": "<string>"
}{
"success": false,
"error": "<string>"
}{
"success": false,
"error": "<string>"
}{
"success": false,
"error": "<string>"
}{
"success": false,
"error": "<string>"
}Dedicated
List the BMC's IPMI accounts
Owner only — team members get 404, the same as a stranger. Lists the BMC’s accounts by name and privilege; TenantOS
never returns BMC passwords. host is always null because TenantOS doesn’t expose the BMC address. Needs a manageable
billing status. Any failure after the access checks (TenantOS unreachable or otherwise) answers 502.
GET
/
v1
/
dedicated
/
{id}
/
ipmi
List the BMC's IPMI accounts
curl --request GET \
--url https://my.server.express/api/v1/dedicated/{id}/ipmi \
--header 'Authorization: Bearer <token>'const options = {method: 'GET', headers: {Authorization: 'Bearer <token>'}};
fetch('https://my.server.express/api/v1/dedicated/{id}/ipmi', 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}/ipmi"
headers = {"Authorization": "Bearer <token>"}
response = requests.get(url, headers=headers)
print(response.text){
"success": true,
"data": {
"host": null,
"users": [
{
"id": 123,
"name": "<string>",
"privilege": "OPERATOR",
"enabled": true
}
],
"hasCustomerAccount": true
}
}{
"success": false,
"error": "<string>"
}{
"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.