Move the given resource to the trash. Following this operation, the resource can be restored, using the
restore operation, or permanently deleted using the permanentlyDelete operation.
Third-party applications using this endpoint via OAuth2 must request the following operation scope: api:filesystem-write.
1
2
3
curl -X DELETE \
\t-H "Authorization: Bearer $TOKEN" \
"https://$HOSTNAME/api/v2/filesystem/resources/ri.foundry.main.dataset.c26f11c8-cdb3-4f44-9f5d-9816ea1c82da"| Error Name | ||
|---|---|---|
Trashing | Error Code | INVALID_ARGUMENT |
| Status Code | 400 | |
| Description | Spaces cannot be trashed. | |
| Parameters | resourceRid | |
Trashing | Error Code | INVALID_ARGUMENT |
| Status Code | 400 | |
| Description | Auto-saved Resources cannot be trashed. | |
| Parameters | resourceRid | |
Trashing | Error Code | INVALID_ARGUMENT |
| Status Code | 400 | |
| Description | Hidden Resources cannot be trashed. | |
| Parameters | resourceRid | |
Delete | Error Code | PERMISSION_DENIED |
| Status Code | 403 | |
| Description | Could not delete the Resource. | |
| Parameters | resourceRid | |
Resource | Error Code | NOT_FOUND |
| Status Code | 404 | |
| Description | The given Resource could not be found. | |
| Parameters | resourceRid | |
See Errors for a general overview of errors in the platform.