Linode API

Trusted Device View Returns a single active TrustedDevice for your User.

User View Returns information about a single User on your Account. This command can only be accessed by the unrestricted users of an account.

User's Grants View Returns the full grants structure for the specified account User (other than the account owner, see below for details). This includes all entities on the Account alongside the level of access this User has to each of them. This command can only be accessed by the unrestricted users of an account. The current authenticated User, including the account owner, may view their own grants at the [/profile/grants](/docs/api/profile/#grants-list) endpoint, but will not see entities that they do not have access to.

User Preferences View View a list of user preferences tied to the OAuth client that generated the token making the request. The user preferences endpoints allow consumers of the API to store arbitrary JSON data, such as a user's font size preference or preferred display name. User preferences are available for each OAuth client registered to your account, and as such an account can have multiple user preferences.

Users List Returns a paginated list of Users on your Account. This command can only be accessed by the unrestricted users of an account. Users may access all or part of your Account based on their restricted status and grants. An unrestricted User may access everything on the account, whereas restricted User may only access entities or perform actions they've been given specific grants to.

VLANs List Returns a list of all Virtual Local Area Networks (VLANs) on your Account. VLANs provide a mechanism for secure communication between two or more Linodes that are assigned to the same VLAN and are both within the same Layer 2 broadcast domain. VLANs are created and attached to Linodes by using the `interfaces` property for the following endpoints: - Linode Create ([POST /linode/instances](/docs/api/linode-instances/#linode-create)) - Configuration Profile Create ([POST /linode/instances/{linodeId}/configs](/docs/api/linode-instances/#configuration-profile-create)) - Configuration Profile Update ([PUT /linode/instances/{linodeId}/configs/{configId}](/docs/api/linode-instances/#configuration-profile-update)) There are several ways to detach a VLAN from a Linode: - [Update](/docs/api/linode-instances/#configuration-profile-update) the active Configuration Profile to remove the VLAN interface, then [reboot](/docs/api/linode-instances/#linode-reboot) the Linode. - [Create](/docs/api/linode-instances/#configuration-profile-create) a new Configuration Profile without the VLAN interface, then [reboot](/docs/api/linode-instances/#linode-reboot) the Linode into the new Configuration Profile. - [Delete](/docs/api/linode-instances/#linode-delete) the Linode. **Note:** Only Next Generation Network (NGN) data centers support VLANs. Use the Regions ([/regions](/docs/api/regions/)) endpoint to view the capabilities of data center regions. If a VLAN is attached to your Linode and you attempt to migrate or clone it to a non-NGN data center, the migration or cloning will not initiate. If a Linode cannot be migrated because of an incompatibility, you will be prompted to select a different data center or contact support. **Note:** See the [VLANs Overview](/docs/products/networking/vlans/#technical-specifications) to view additional specifications and limitations.

Volume View Get information about a single Volume.

Volumes List Returns a paginated list of Volumes you have permission to view.

NodeBalancer Statistics View Returns detailed statistics about the requested NodeBalancer.

Domain Import Imports a domain zone from a remote nameserver. Your nameserver must allow zone transfers (AXFR) from the following IPs: - 96.126.114.97 - 96.126.114.98 - 2600:3c00::5e - 2600:3c00::5f

Payment Method Make Default Make the specified Payment Method the default method for automatically processing payments. Removes the default status from any other Payment Method.

DC Migration/Pending Host Migration Initiate Initiate a pending host migration that has been scheduled by Linode or initiate a cross data center (DC) migration. A list of pending migrations, if any, can be accessed from [GET /account/notifications](/docs/api/account/#notifications-list). When the migration begins, your Linode will be shutdown if not already off. If the migration initiated the shutdown, it will reboot the Linode when completed. To initiate a cross DC migration, you must pass a `region` parameter to the request body specifying the target data center region. You can view a list of all available regions and their feature capabilities from [GET /regions](/docs/api/regions/#regions-list). If your Linode has a DC migration already queued or you have initiated a previously scheduled migration, you will not be able to initiate a DC migration until it has completed. **Note:** Next Generation Network (NGN) data centers do not support IPv6 `/116` pools or IP Failover. If you have these features enabled on your Linode and attempt to migrate to an NGN data center, the migration will not initiate. If a Linode cannot be migrated because of an incompatibility, you will be prompted to select a different data center or contact support.

Object Storage Bucket Access Modify Allows changing basic Cross-origin Resource Sharing (CORS) and Access Control Level (ACL) settings. Only allows enabling/disabling CORS for all origins, and/or setting canned ACLs. For more fine-grained control of both systems, please use the more [fully-featured S3 API](https://docs.ceph.com/en/latest/radosgw/s3/bucketops/#put-bucket-acl) directly.

Linode Upgrade Linodes created with now-deprecated Types are entitled to a free upgrade to the next generation. A mutating Linode will be allocated any new resources the upgraded Type provides, and will be subsequently restarted if it was currently running. If any actions are currently running or queued, those actions must be completed first before you can initiate a mutate.

Managed MongoDB Database Backup Snapshot Create Creates a snapshot backup of a Managed MongoDB Database. Requires `read_write` access to the Database. Up to 3 snapshot backups for each Database can be stored at a time. If 3 snapshots have been created for a Database, one must be deleted before another can be made. Backups generated by this command have the type `snapshot`. Snapshot backups may take several minutes to complete, after which they will be accessible to view or restore. The Database must have an `active` status to perform this command. If another backup is in progress, it must complete before a new backup can be initiated. **Note**: New MongoDB Databases cannot currently be created.

Managed MongoDB Database Backup Restore Restore a backup to a Managed MongoDB Database on your Account. Requires `read_write` access to the Database. The Database must have an `active` status to perform this command. **Note**: Restoring from a backup will erase all existing data on the database instance and replace it with backup data. **Note**: Currently, restoring a backup after resetting Managed Database credentials results in a failed cluster. Please contact Customer Support if this occurs. **Note**: New MongoDB Databases cannot currently be created.

Managed MongoDB Database Credentials Reset Reset the root password for a Managed MongoDB Database. Requires `read_write` access to the Database. A new root password is randomly generated and accessible with the **Managed MongoDB Database Credentials View** ([GET /databases/mongodb/instances/{instanceId}/credentials](/docs/api/databases/#managed-mongodb-database-credentials-view)) command. Only unrestricted Users can access this command, and have access regardless of the acting token's OAuth scopes. **Note**: Note that it may take several seconds for credentials to reset. **Note**: New MongoDB Databases cannot currently be created.

Managed MongoDB Database Patch Apply security patches and updates to the underlying operating system of the Managed MongoDB Database. This function runs during regular maintenance windows, which are configurable with the **Managed MongoDB Database Update** ([PUT /databases/mongodb/instances/{instanceId}](/docs/api/databases/#managed-mongodb-database-update)) command. Requires `read_write` access to the Database. The Database must have an `active` status to perform this command. **Note**: * If your database cluster is configured with a single node, you will experience downtime during this maintenance. Consider upgrading to a high availability plan to avoid any downtime due to maintenance. * **The database software is not updated automatically.** To upgrade to a new database engine version, consider deploying a new Managed Database with your preferred version. You can then migrate your databases from the original Managed Database cluster to the new one. **Note**: New MongoDB Databases cannot currently be created.

Managed MySQL Database Backup Snapshot Create Creates a snapshot backup of a Managed MySQL Database. Requires `read_write` access to the Database. Up to 3 snapshot backups for each Database can be stored at a time. If 3 snapshots have been created for a Database, one must be deleted before another can be made. Backups generated by this command have the type `snapshot`. Snapshot backups may take several minutes to complete, after which they will be accessible to view or restore. The Database must have an `active` status to perform this command. If another backup is in progress, it must complete before a new backup can be initiated.

Managed MySQL Database Backup Restore Restore a backup to a Managed MySQL Database on your Account. Requires `read_write` access to the Database. The Database must have an `active` status to perform this command. **Note**: Restoring from a backup will erase all existing data on the database instance and replace it with backup data. **Note**: Currently, restoring a backup after resetting Managed Database credentials results in a failed cluster. Please contact Customer Support if this occurs.

Managed MySQL Database Credentials Reset Reset the root password for a Managed MySQL Database. Requires `read_write` access to the Database. A new root password is randomly generated and accessible with the **Managed MySQL Database Credentials View** ([GET /databases/mysql/instances/{instanceId}/credentials](/docs/api/databases/#managed-mysql-database-credentials-view)) command. Only unrestricted Users can access this command, and have access regardless of the acting token's OAuth scopes. **Note**: Note that it may take several seconds for credentials to reset.

Managed MySQL Database Patch Apply security patches and updates to the underlying operating system of the Managed MySQL Database. This function runs during regular maintenance windows, which are configurable with the **Managed MySQL Database Update** ([PUT /databases/mysql/instances/{instanceId}](/docs/api/databases/#managed-mysql-database-update)) command. Requires `read_write` access to the Database. The Database must have an `active` status to perform this command. **Note** * If your database cluster is configured with a single node, you will experience downtime during this maintenance. Consider upgrading to a high availability plan to avoid any downtime due to maintenance. * **The database software is not updated automatically.** To upgrade to a new database engine version, consider deploying a new Managed Database with your preferred version. You can then [migrate your databases](/docs/products/databases/managed-databases/guides/migrate-mysql/) from the original Managed Database cluster to the new one.

Managed MySQL Database Create Provision a Managed MySQL Database. Restricted Users must have the `add_databases` grant to use this command. New instances can take approximately 15 to 30 minutes to provision. The `allow_list` is used to control access to the Managed Database. * IP addresses and ranges in this list can access the Managed Database. All other sources are blocked. * If `0.0.0.0/0` is a value in this list, then all IP addresses can access the Managed Database. * Entering an empty array (`[]`) blocks all connections (both public and private) to the Managed Database. All Managed Databases include automatic, daily backups. Up to seven backups are automatically stored for each Managed Database, providing restore points for each day of the past week. All Managed Databases include automatic patch updates, which apply security patches and updates to the underlying operating system of the Managed MySQL Database during configurable maintenance windows. * If your database cluster is configured with a single node, you will experience downtime during this maintenance window when any updates occur. It's recommended that you adjust this window to match a time that will be the least disruptive for your application and users. You may also want to consider upgrading to a high availability plan to avoid any downtime due to maintenance. * **The database software is not updated automatically.** To upgrade to a new database engine version, consider deploying a new Managed Database with your preferred version. You can then [migrate your databases](/docs/products/databases/managed-databases/guides/migrate-mysql/) from the original Managed Database cluster to the new one. * To modify update the maintenance window for a Database, use the **Managed MySQL Database Update** ([PUT /databases/mysql/instances/{instanceId}](/docs/api/databases/#managed-mysql-database-update)) command.

Managed PostgreSQL Database Backup Snapshot Create Creates a snapshot backup of a Managed PostgreSQL Database. Requires `read_write` access to the Database. Up to 3 snapshot backups for each Database can be stored at a time. If 3 snapshots have been created for a Database, one must be deleted before another can be made. Backups generated by this command have the type `snapshot`. Snapshot backups may take several minutes to complete, after which they will be accessible to view or restore. The Database must have an `active` status to perform this command. If another backup is in progress, it must complete before a new backup can be initiated.

Managed PostgreSQL Database Backup Restore Restore a backup to a Managed PostgreSQL Database on your Account. Requires `read_write` access to the Database. The Database must have an `active` status to perform this command. **Note**: Restoring from a backup will erase all existing data on the database instance and replace it with backup data. **Note**: Currently, restoring a backup after resetting Managed Database credentials results in a failed cluster. Please contact Customer Support if this occurs.

Managed PostgreSQL Database Credentials Reset Reset the root password for a Managed PostgreSQL Database. Requires `read_write` access to the Database. A new root password is randomly generated and accessible with the **Managed PostgreSQL Database Credentials View** ([GET /databases/postgresql/instances/{instanceId}/credentials](/docs/api/databases/#managed-postgresql-database-credentials-view)) command. Only unrestricted Users can access this command, and have access regardless of the acting token's OAuth scopes. **Note**: Note that it may take several seconds for credentials to reset.

Managed PostgreSQL Database Patch Apply security patches and updates to the underlying operating system of the Managed PostgreSQL Database. This function runs during regular maintenance windows, which are configurable with the **Managed PostgreSQL Database Update** ([PUT /databases/postgresql/instances/{instanceId}](/docs/api/databases/#managed-postgresql-database-update)) command. Requires `read_write` access to the Database. The Database must have an `active` status to perform this command. **Note** * If your database cluster is configured with a single node, you will experience downtime during this maintenance. Consider upgrading to a high availability plan to avoid any downtime due to maintenance. * **The database software is not updated automatically.** To upgrade to a new database engine version, consider deploying a new Managed Database with your preferred version. You can then migrate your databases from the original Managed Database cluster to the new one.

Managed PostgreSQL Database Create Provision a Managed PostgreSQL Database. Restricted Users must have the `add_databases` grant to use this command. New instances can take approximately 15 to 30 minutes to provision. The `allow_list` is used to control access to the Managed Database. * IP addresses and ranges in this list can access the Managed Database. All other sources are blocked. * If `0.0.0.0/0` is a value in this list, then all IP addresses can access the Managed Database. * Entering an empty array (`[]`) blocks all connections (both public and private) to the Managed Database. All Managed Databases include automatic, daily backups. Up to seven backups are automatically stored for each Managed Database, providing restore points for each day of the past week. All Managed Databases include automatic patch updates, which apply security patches and updates to the underlying operating system of the Managed PostgreSQL Database during configurable maintenance windows. * If your database cluster is configured with a single node, you will experience downtime during this maintenance window when any updates occur. It's recommended that you adjust this window to match a time that will be the least disruptive for your application and users. You may also want to consider upgrading to a high availability plan to avoid any downtime due to maintenance. * **The database software is not updated automatically.** To upgrade to a new database engine version, consider deploying a new Managed Database with your preferred version. You can then migrate your databases from the original Managed Database cluster to the new one. * To modify update the maintenance window for a Database, use the **Managed PostgreSQL Database Update** ([PUT /databases/postgresql/instances/{instanceId}](/docs/api/databases/#managed-postgresql-database-update)) command.

IPv6 Range Create Creates an IPv6 Range and assigns it based on the provided Linode or route target IPv6 SLAAC address. See the `ipv6` property when accessing the Linode View ([GET /linode/instances/{linodeId}](/docs/api/linode-instances/#linode-view)) endpoint to view a Linode's IPv6 SLAAC address. * Either `linode_id` or `route_target` is required in a request. * `linode_id` and `route_target` are mutually exclusive. Submitting values for both properties in a request results in an error. * Upon a successful request, an IPv6 range is created in the [Region](/docs/api/regions/#regions-list) that corresponds to the provided `linode_id` or `route_target`. * Your Linode is responsible for routing individual addresses in the range, or handling traffic for all the addresses in the range. * Access the IP Addresses Assign ([POST /networking/ips/assign](/docs/api/networking/#ip-addresses-assign)) endpoint to re-assign IPv6 Ranges to your Linodes. **Note**: The following restrictions apply: * A Linode can only have one IPv6 range targeting its SLAAC address. * An account can only have one IPv6 range in each [Region](/docs/api/regions/#regions-list). * [Open a Support Ticket](/docs/api/support/#support-ticket-open) to request expansion of these restrictions.

Service Token Delete Delete and regenerate the service account token for a Cluster. **Note**: When regenerating a service account token, the Cluster's control plane components and Linode CSI drivers are also restarted and configured with the new token. High Availability Clusters should not experience any disruption, while standard Clusters may experience brief control plane downtime while components are restarted.

Node Recycle Recycles an individual Node in the designated Kubernetes Cluster. The Node will be deleted and replaced with a new Linode, which may take a few minutes. Replacement Nodes are installed with the latest available patch for the Cluster's Kubernetes Version. **Any local storage on deleted Linodes (such as "hostPath" and "emptyDir" volumes, or "local" PersistentVolumes) will be erased.**

Node Pool Recycle Recycles a Node Pool for the designated Kubernetes Cluster. All Linodes within the Node Pool will be deleted and replaced with new Linodes on a rolling basis, which may take several minutes. Replacement Nodes are installed with the latest available patch for the Cluster's Kubernetes Version. **Any local storage on deleted Linodes (such as "hostPath" and "emptyDir" volumes, or "local" PersistentVolumes) will be erased.**

Node Pool Create Creates a new Node Pool for the designated Kubernetes cluster.

Cluster Nodes Recycle Recycles all nodes in all pools of a designated Kubernetes Cluster. All Linodes within the Cluster will be deleted and replaced with new Linodes on a rolling basis, which may take several minutes. Replacement Nodes are installed with the latest available [patch version](https://github.com/kubernetes/community/blob/master/contributors/design-proposals/release/versioning.md#kubernetes-release-versioning) for the Cluster's current Kubernetes minor release. **Any local storage on deleted Linodes (such as "hostPath" and "emptyDir" volumes, or "local" PersistentVolumes) will be erased.**

Kubernetes Cluster Regenerate Regenerate the Kubeconfig file and/or the service account token for a Cluster. This is a helper command that allows performing both the [Kubeconfig Delete](#kubeconfig-delete) and the [Service Token Delete](#service-token-delete) actions with a single request. When using this command, at least one of `kubeconfig` or `servicetoken` is required. **Note**: When regenerating a service account token, the Cluster's control plane components and Linode CSI drivers are also restarted and configured with the new token. High Availability Clusters should not experience any disruption, while standard Clusters may experience brief control plane downtime while components are restarted.

Phone Number Verification Code Send Send a one-time verification code via SMS message to the submitted phone number. Providing your phone number helps ensure you can securely access your Account in case other ways to connect are lost. Your phone number is only used to verify your identity by sending an SMS message. Standard carrier messaging fees may apply. * By accessing this command you are opting in to receive SMS messages. You can opt out of SMS messages by using the **Phone Number Delete** ([DELETE /profile/phone-number](/docs/api/profile/#phone-number-delete)) command after your phone number is verified. * Verification codes are valid for 10 minutes after they are sent. * Subsequent requests made prior to code expiration result in sending the same code. Once a verification code is received, verify your phone number with the **Phone Number Verify** ([POST /profile/phone-number/verify](/docs/api/profile/#phone-number-verify)) command.

Phone Number Verify Verify a phone number by confirming the one-time code received via SMS message after accessing the **Phone Verification Code Send** ([POST /profile/phone-number](/docs/api/profile/#phone-number-verification-code-send)) command. * Verification codes are valid for 10 minutes after they are sent. * Only the same User that made the verification code request can use that code with this command. Once completed, the verified phone number is assigned to the User making the request. To change the verified phone number for a User, first use the **Phone Number Delete** ([DELETE /profile/phone-number](/docs/api/profile/#phone-number-delete)) command, then begin the verification process again with the **Phone Verification Code Send** ([POST /profile/phone-number](/docs/api/profile/#phone-number-verification-code-send)) command.

Security Questions Answer Adds security question responses for your User. Requires exactly three unique questions. Previous responses are overwritten if answered or reset to `null` if unanswered. **Note**: Security questions must be answered for your User prior to accessing the **Two Factor Secret Create** ([POST /profile/tfa-enable](/docs/api/profile/#two-factor-secret-create)) command.

Image Upload Initiates an Image upload. This endpoint creates a new private Image object and returns it along with the URL to which image data can be uploaded. - Image data must be uploaded within 24 hours of creation or the upload will be cancelled and the image deleted. - Image uploads should be made as an HTTP PUT request to the URL returned in the `upload_to` response parameter, with a `Content-type: application/octet-stream` header included in the request. For example: curl -v \ -H "Content-Type: application/octet-stream" \ --upload-file example.img.gz \ $UPLOAD_URL \ --progress-bar \ --output /dev/null - Uploaded image data should be compressed in gzip (`.gz`) format. The uncompressed disk should be in raw disk image (`.img`) format. A maximum compressed file size of 5GB is supported for upload at this time. **Note:** To initiate and complete an Image upload in a single step, see our guide on how to [Upload an Image](/docs/products/tools/images/guides/upload-an-image/) using Cloud Manager or the Linode CLI `image-upload` plugin.

Managed MongoDB Database Update Update a Managed MongoDB Database. Requires `read_write` access to the Database. The Database must have an `active` status to perform this command. Updating addresses in the `allow_list` overwrites any existing addresses. * IP addresses and ranges on this list can access the Managed Database. All other sources are blocked. * If `0.0.0.0/0` is a value in this list, then all IP addresses can access the Managed Database. * Entering an empty array (`[]`) blocks all connections (both public and private) to the Managed Database. * **Note**: Updates to the `allow_list` may take a short period of time to complete, making this command inappropriate for rapid successive updates to this property. All Managed Databases include automatic patch updates, which apply security patches and updates to the underlying operating system of the Managed MongoDB Database. The maintenance window for these updates is configured with the Managed Database's `updates` property. * If your database cluster is configured with a single node, you will experience downtime during this maintenance window when any updates occur. It's recommended that you adjust this window to match a time that will be the least disruptive for your application and users. You may also want to consider upgrading to a high availability plan to avoid any downtime due to maintenance. * **The database software is not updated automatically.** To upgrade to a new database engine version, consider deploying a new Managed Database with your preferred version. You can then migrate your databases from the original Managed Database cluster to the new one. **Note**: New MongoDB Databases cannot currently be created.

Managed MySQL Database Update Update a Managed MySQL Database. Requires `read_write` access to the Database. The Database must have an `active` status to perform this command. Updating addresses in the `allow_list` overwrites any existing addresses. * IP addresses and ranges in this list can access the Managed Database. All other sources are blocked. * If `0.0.0.0/0` is a value in this list, then all IP addresses can access the Managed Database. * Entering an empty array (`[]`) blocks all connections (both public and private) to the Managed Database. * **Note**: Updates to the `allow_list` may take a short period of time to complete, making this command inappropriate for rapid successive updates to this property. All Managed Databases include automatic patch updates, which apply security patches and updates to the underlying operating system of the Managed MySQL Database. The maintenance window for these updates is configured with the Managed Database's `updates` property. * If your database cluster is configured with a single node, you will experience downtime during this maintenance window when any updates occur. It's recommended that you adjust this window to match a time that will be the least disruptive for your application and users. You may also want to consider upgrading to a high availability plan to avoid any downtime due to maintenance. * **The database software is not updated automatically.** To upgrade to a new database engine version, consider deploying a new Managed Database with your preferred version. You can then [migrate your databases](/docs/products/databases/managed-databases/guides/migrate-mysql/) from the original Managed Database cluster to the new one.

Managed PostgreSQL Database Update Update a Managed PostgreSQL Database. Requires `read_write` access to the Database. The Database must have an `active` status to perform this command. Updating addresses in the `allow_list` overwrites any existing addresses. * IP addresses and ranges in this list can access the Managed Database. All other sources are blocked. * If `0.0.0.0/0` is a value in this list, then all IP addresses can access the Managed Database. * Entering an empty array (`[]`) blocks all connections (both public and private) to the Managed Database. * **Note**: Updates to the `allow_list` may take a short period of time to complete, making this command inappropriate for rapid successive updates to this property. All Managed Databases include automatic patch updates, which apply security patches and updates to the underlying operating system of the Managed PostgreSQL Database. The maintenance window for these updates is configured with the Managed Database's `updates` property. * If your database cluster is configured with a single node, you will experience downtime during this maintenance window when any updates occur. It's recommended that you adjust this window to match a time that will be the least disruptive for your application and users. You may also want to consider upgrading to a high availability plan to avoid any downtime due to maintenance. * **The database software is not updated automatically.** To upgrade to a new database engine version, consider deploying a new Managed Database with your preferred version. You can then migrate your databases from the original Managed Database cluster to the new one.

Kubernetes Cluster Update Updates a Kubernetes cluster.

Node Pool Update Updates a Node Pool's count and autoscaler configuration. Linodes will be created or deleted to match changes to the Node Pool's count. **Any local storage on deleted Linodes (such as "hostPath" and "emptyDir" volumes, or "local" PersistentVolumes) will be erased.**

Linode Reboot Reboots a Linode you have permission to modify. If any actions are currently running or queued, those actions must be completed first before you can initiate a reboot.

Linode Rebuild Rebuilds a Linode you have the `read_write` permission to modify. A rebuild will first shut down the Linode, delete all disks and configs on the Linode, and then deploy a new `image` to the Linode with the given attributes. Additionally: * Requires an `image` be supplied. * Requires a `root_pass` be supplied to use for the root User's Account. * It is recommended to supply SSH keys for the root User using the `authorized_keys` field.

Config Rebuild Rebuilds a NodeBalancer Config and its Nodes that you have permission to modify. Use this command to update a NodeBalancer's Config and Nodes with a single request.

IPv4 Address Delete Deletes a public or private IPv4 address associated with this Linode. This will fail if it is the Linode's last remaining public IPv4 address.

Linode Boot into Rescue Mode Rescue Mode is a safe environment for performing many system recovery and disk management tasks. Rescue Mode is based on the Finnix recovery distribution, a self-contained and bootable Linux distribution. You can also use Rescue Mode for tasks other than disaster recovery, such as formatting disks to use different filesystems, copying data between disks, and downloading files from a disk via SSH and SFTP. * Note that "sdh" is reserved and unavailable during rescue.

OAuth Client Secret Reset Resets the OAuth Client secret for a client you own, and returns the OAuth Client with the plaintext secret. This secret is not supposed to be publicly known or disclosed anywhere. This can be used to generate a new secret in case the one you have has been leaked, or to get a new secret if you lost the original. The old secret is expired immediately, and logins to your client with the old secret will fail.