# Terminate Twin
This endpoint terminates a given Twin. The termination of a Twin cannot be undone. Only the owner of a Twin can terminate a Twin.
The termination of a Twin is permanent and cannot be undone. After the termination of a Twin, the owner of the Twin will not be able to update the
"description" field of the Twin. However, Ledger Entries, Identities, and Docs can be attached to terminated Twins by all users involved in the process.
In order for a user to perform the "terminate_twin" operation, the "terminate_twin" permission must be included in the list of allowed actions in the statement of the user's role.
|owner||string||Account UUID of the account which is the current owner of the Twin.|
|status||string, value is ||The status of a Twin can be |
|updated_ts||timestamp||Time at which the Twin was last updated. Measured in seconds (to three decimal places) that have elapsed since the Unix epoch(opens new window).|
|description||dictionary||Attributes of the Twin defined by the owner in form of key-value pairs:|
- key: It must match the regular expression(opens new window)
- value: JSON compliant value. Only the owner of the Twin can update the
For more details consult the description section.
Certificate generated automatically by the system upon creation of the Twin. It cannot be modified after it has been generated.
Certificate generated automatically by the system when the Twin is terminated. It cannot be modified after it has been generated.
# Status codes
Requests to this endpoint result in generic status codes. For a comprehensive list of status codes, please consult the Status codes section.