undelete end point changed to the same one as delete for workspaces a…

…nd files
vispower · Sep 27, 2012 · 9abae0f · 9abae0f
1 parent 9045034
commit 9abae0f
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 14 deletions.
diff --git a/file.md b/file.md
@@ -189,12 +189,6 @@ Delete, Undelete and Purge file
 
 * `DELETE /files/1` will delete the file and return `200 Ok` if that was successful. If the user does not have access to delete the file, you'll see `403 Forbidden`.
 
-* `PUT /files/1` with the following JSON(with blank `deleted_at` parameter) will undelete the file and return `200 Ok` if that was successful. If the user does not have access to undelete the file, you'll see `403 Forbidden`.
-
-```json
-{
-  "deleted_at": ""
-}
-```
+* `DELETE /files/1?undelete=true` will undelete the file and return `200 Ok` if that was successful. If the user does not have access to undelete the file, you'll see `403 Forbidden`.
 
 * `DELETE /files/1?purge=true` will permanently delete the file and return `204 No Content` if that was successful. If the user does not have access to purge the file, you'll see `403 Forbidden`.
diff --git a/workspace.md b/workspace.md
@@ -133,12 +133,6 @@ Delete, Undelete and Purge workspace
 
 * `DELETE /workspaces/1` will delete the workspace specified and return `200 Ok` if that was successful. If the user does not have access to delete the workspace, you'll see `403 Forbidden`.
 
-* `PUT /workspaces/1` with the following JSON(with blank `deleted_at` parameter) will undelete the workspace and return `200 Ok` if that was successful. If the user does not have access to undelete the workspace, you'll see `403 Forbidden`.
-
-```json
-{
-  "deleted_at": ""
-}
-```
+* `DELETE /workspaces/1?undelete=true` will undelete the workspace and return `200 Ok` if that was successful. If the user does not have access to undelete the workspace, you'll see `403 Forbidden`.
 
 * `DELETE /workspaces/1?purge=true` will permanently delete the workspace and return `204 No Content` if that was successful. If the user does not have access to purge the workspace, you'll see `403 Forbidden`.