# Destroy With Associated Resources
## List
**get** `/v2/droplets/{droplet_id}/destroy_with_associated_resources`
To list the associated billable resources that can be destroyed along with a
Droplet, send a GET request to the
`/v2/droplets/$DROPLET_ID/destroy_with_associated_resources` endpoint.
This endpoint will only return resources that you are authorized to see. For
example, to see associated Reserved IPs, include the `reserved_ip:read` scope.
The response will be a JSON object containing `snapshots`, `volumes`, and
`volume_snapshots` keys. Each will be set to an array of objects containing
information about the associated resources.
### Returns
- **floating\_ips:** `array of AssociatedResource`
Floating IPs that are associated with this Droplet.
Requires `reserved_ip:read` scope.
- **reserved\_ips:** `array of AssociatedResource`
Reserved IPs that are associated with this Droplet.
Requires `reserved_ip:read` scope.
- **snapshots:** `array of AssociatedResource`
Snapshots that are associated with this Droplet.
Requires `image:read` scope.
- **volume\_snapshots:** `array of AssociatedResource`
Volume Snapshots that are associated with this Droplet.
Requires `block_storage_snapshot:read` scope.
- **volumes:** `array of AssociatedResource`
Volumes that are associated with this Droplet.
Requires `block_storage:read` scope.
## Check Status
**get** `/v2/droplets/{droplet_id}/destroy_with_associated_resources/status`
To check on the status of a request to destroy a Droplet with its associated
resources, send a GET request to the
`/v2/droplets/$DROPLET_ID/destroy_with_associated_resources/status` endpoint.
### Returns
- **completed\_at:** `string`
A time value given in ISO8601 combined date and time format indicating when the requested action was completed.
- **droplet:** `DestroyedAssociatedResource`
An object containing information about a resource scheduled for deletion.
- **failures:** `number`
A count of the associated resources that failed to be destroyed, if any.
- **resources:** `object { floating_ips, reserved_ips, snapshots, 2 more }`
An object containing additional information about resource related to a Droplet requested to be destroyed.
- **floating\_ips:** `array of DestroyedAssociatedResource`
- **reserved\_ips:** `array of DestroyedAssociatedResource`
- **snapshots:** `array of DestroyedAssociatedResource`
- **volume\_snapshots:** `array of DestroyedAssociatedResource`
- **volumes:** `array of DestroyedAssociatedResource`
## Delete Dangerous
**delete** `/v2/droplets/{droplet_id}/destroy_with_associated_resources/dangerous`
To destroy a Droplet along with all of its associated resources, send a DELETE
request to the `/v2/droplets/$DROPLET_ID/destroy_with_associated_resources/dangerous`
endpoint. The headers of this request must include an `X-Dangerous` key set to
`true`. To preview which resources will be destroyed, first query the
Droplet's associated resources. This operation _can not_ be reverse and should
be used with caution.
A successful response will include a 202 response code and no content. Use the
status endpoint to check on the success or failure of the destruction of the
individual resources.
## Delete Selective
**delete** `/v2/droplets/{droplet_id}/destroy_with_associated_resources/selective`
To destroy a Droplet along with a sub-set of its associated resources, send a
DELETE request to the `/v2/droplets/$DROPLET_ID/destroy_with_associated_resources/selective`
endpoint. The JSON body of the request should include `reserved_ips`, `snapshots`, `volumes`,
or `volume_snapshots` keys each set to an array of IDs for the associated
resources to be destroyed. The IDs can be found by querying the Droplet's
associated resources. Any associated resource not included in the request
will remain and continue to accrue changes on your account.
A successful response will include a 202 response code and no content. Use
the status endpoint to check on the success or failure of the destruction of
the individual resources.
## Retry
**post** `/v2/droplets/{droplet_id}/destroy_with_associated_resources/retry`
If the status of a request to destroy a Droplet with its associated resources
reported any errors, it can be retried by sending a POST request to the
`/v2/droplets/$DROPLET_ID/destroy_with_associated_resources/retry` endpoint.
Only one destroy can be active at a time per Droplet. If a retry is issued
while another destroy is in progress for the Droplet a 409 status code will
be returned. A successful response will include a 202 response code and no
content.
## Domain Types
### Associated Resource
- **AssociatedResource:** `object { id, cost, name }`
An objects containing information about a resource associated with a Droplet.
- **id:** `string`
The unique identifier for the resource associated with the Droplet.
- **cost:** `string`
The cost of the resource in USD per month if the resource is retained after the Droplet is destroyed.
- **name:** `string`
The name of the resource associated with the Droplet.
### Destroyed Associated Resource
- **DestroyedAssociatedResource:** `object { id, destroyed_at, error_message, name }`
An object containing information about a resource scheduled for deletion.
- **id:** `string`
The unique identifier for the resource scheduled for deletion.
- **destroyed\_at:** `string`
A time value given in ISO8601 combined date and time format indicating when the resource was destroyed if the request was successful.
- **error\_message:** `string`
A string indicating that the resource was not successfully destroyed and providing additional information.
- **name:** `string`
The name of the resource scheduled for deletion.