Managed
Managed Linode Settings List
https://api.linode.com/v4/managed/linode-settings
Returns a paginated list of Managed Settings for your Linodes. There will be one entry per Linode on your Account.
This command can only be accessed by the unrestricted users of an account.
Query Parameters
The page of a collection to return.
The number of items to return per page.
Request Samples
- Shell
- CLI
curl -H "Authorization: Bearer $TOKEN" \
https://api.linode.com/v4/managed/linode-settings
Response Samples
- 200
- default
{
"data": [
{
"id": "",
"label": "linode123",
"group": "linodes",
"ssh": {
"access": true,
"user": "linode",
"ip": "203.0.113.1",
"port": 22
}
}
],
"page": 1,
"pages": 1,
"results": 1
}Responses
200: A paginated list of Managed settings for your Linodes.
The ID of the Linode these Settings are for.
The label of the Linode these Settings are for.
The group of the Linode these Settings are for. This is for display purposes only.
The SSH settings for this Linode.
If true, Linode special forces may access this Linode over ssh to respond to Issues.
The specific user, if any, Linode's special forces should use when accessing this Linode to respond to an issue.
The default null value corresponds to the root user.
The IP Linode special forces should use to access this Linode when responding to an Issue.
By default, any of a Linode's IP addresses can be used for incident response access.
The port Linode special forces should use to access this Linode over ssh to respond to an Issue.
The default null value corresponds to port 22.
The current page.
The total number of pages.
The total number of results.
default: Error
What happened to cause this error. In most cases, this can be fixed immediately by changing the data you sent in the request, but in some cases you will be instructed to open a Support Ticket or perform some other action before you can complete the request successfully.
The field in the request that caused this error. This may be a path, separated by periods in the case of nested fields. In some cases this may come back as "null" if the error is not specific to any single element of the request.