service_transfers

Overview

Name	service_transfers
Type	Resource
Id	linode.account.service_transfers

Fields

Name	Datatype	Description
created	string	When this transfer was created.
entities	object	A collection of the services to include in this transfer request, separated by type.
expiry	string	When this transfer expires. Transfers will automatically expire 24 hours after creation.
is_sender	boolean	If the requesting account created this transfer.
status	string	The status of the transfer request. accepted: The transfer has been accepted by another user and is currently in progress. Transfers can take up to 3 hours to complete. cancelled: The transfer has been cancelled by the sender. completed: The transfer has completed successfully. failed: The transfer has failed after initiation. pending: The transfer is ready to be accepted. stale: The transfer has exceeded its expiration date. It can no longer be accepted or cancelled.
token	string	The token used to identify and accept or cancel this transfer.
updated	string	When this transfer was last updated.

Methods

Name	Accessible by	Required Params	Description
getServiceTransfer	SELECT	token	Returns the details of the Service Transfer for the provided token. While a transfer is pending, any unrestricted user of any account can access this command. After a transfer has been accepted, it can only be viewed by unrestricted users of the accounts that created and accepted the transfer. If cancelled or expired, only unrestricted users of the account that created the transfer can view it.
getServiceTransfers	SELECT		Returns a collection of all created and accepted Service Transfers for this account, regardless of the user that created or accepted the transfer. This command can only be accessed by the unrestricted users of an account.
createServiceTransfer	INSERT	data__entities	Creates a transfer request for the specified services. A request can contain any of the specified service types and any number of each service type. At this time, only Linodes can be transferred. When created successfully, a confirmation email is sent to the account that created this transfer containing a transfer token and instructions on completing the transfer. When a transfer is accepted, the requested services are moved to the receiving account. Linode services will not experience interruptions due to the transfer process. Backups for Linodes are transferred as well. DNS records that are associated with requested services will not be transferred or updated. Please ensure that associated DNS records have been updated or communicated to the recipient prior to the transfer. A transfer can take up to three hours to complete once accepted. When a transfer is completed, billing for transferred services ends for the sending account and begins for the receiving account. This command can only be accessed by the unrestricted users of an account. There are several conditions that must be met in order to successfully create a transfer request: 1. The account creating the transfer must not have a past due balance or active Terms of Service violation. 1. The service must be owned by the account that is creating the transfer. 1. The service must not be assigned to another Service Transfer that is pending or that has been accepted and is incomplete. 1. Linodes must not: be assigned to a NodeBalancer, Firewall, VLAN, or Managed Service. have any attached Block Storage Volumes. have any shared IP addresses. have any assigned /56, /64, or /116 IPv6 ranges.
deleteServiceTransfer	DELETE	token	Cancels the Service Transfer for the provided token. Once cancelled, a transfer cannot be accepted or otherwise acted on in any way. If cancelled in error, the transfer must be created again. When cancelled, an email notification for the cancellation is sent to the account that created this transfer. Transfers can not be cancelled if they are expired or have been accepted. This command can only be accessed by the unrestricted users of the account that created this transfer.
_getServiceTransfer	EXEC	token	Returns the details of the Service Transfer for the provided token. While a transfer is pending, any unrestricted user of any account can access this command. After a transfer has been accepted, it can only be viewed by unrestricted users of the accounts that created and accepted the transfer. If cancelled or expired, only unrestricted users of the account that created the transfer can view it.
_getServiceTransfers	EXEC		Returns a collection of all created and accepted Service Transfers for this account, regardless of the user that created or accepted the transfer. This command can only be accessed by the unrestricted users of an account.
acceptServiceTransfer	EXEC	token	Accept a Service Transfer for the provided token to receive the services included in the transfer to your account. At this time, only Linodes can be transferred. When accepted, email confirmations are sent to the accounts that created and accepted the transfer. A transfer can take up to three hours to complete once accepted. Once a transfer is completed, billing for transferred services ends for the sending account and begins for the receiving account. This command can only be accessed by the unrestricted users of the account that receives the transfer. Users of the same account that created a transfer cannot accept the transfer. There are several conditions that must be met in order to accept a transfer request: 1. Only transfers with a pending status can be accepted. 1. The account accepting the transfer must have a registered payment method and must not have a past due balance or other account limitations for the services to be transferred. 1. Both the account that created the transfer and the account that is accepting the transfer must not have any active Terms of Service violations. 1. The service must still be owned by the account that created the transfer. 1. Linodes must not: be assigned to a NodeBalancer, Firewall, VLAN, or Managed Service. have any attached Block Storage Volumes. have any shared IP addresses. have any assigned /56, /64, or /116 IPv6 ranges. Any and all of the above conditions must be cured and maintained by the relevant account prior to the transfer's expiration to allow the transfer to be accepted by the receiving account.