Deleting a folder
Added by IBM contributorIBM | Edited by IBM contributorElizabeth Bowling on August 21, 2015
Rate this article 1 starsRate this article 2 starsRate this article 3 starsRate this article 4 starsRate this article 5 stars

Delete a file folder using the HTTP DELETE request. Deleting a folder does not delete the files in the folder.

Only a manager of a folder can delete the folder.

Note: {collection-id} is the value of the <td:uuid> element in the collection's Atom entry document.

You can use this input header in a POST request instead of using the DELETE request.

This method requires authentication.

Input
Method URI Description
DELETE /files/{auth}/api/collection/{collection-id}/entry Delete a file folder using the HTTP DELETE request.
Name Type Optional Description
collection-id
string No {collection-id} is the value of the <td:uuid> element in the collection's Atom entry document.
auth
enumerated No The authorization protocol being used by your application to access Connections Cloud.
Authorized values:
  • basic
  • oauth
Name Type Optional Description
X-Method-Override
string Yes Tunnels a DELETE request over HTTP POST
X-Update-Nonce
string Yes String. Represents a unique data string generated by the server upon request that you can provide to secure the request. See Getting a nonce key for information about how to request the data string.
Authorization
enumerated No The authentication mechanism selected by your application to access the API.
Basic is the Base64 encoding of the IBM Connections Cloud username and password: Base64(username:password). For example, Base64(twatson@us.ibm.com:password).
Bearer is the oauth 2.0 access token that is generated when the user grants your application access to IBM Connections Cloud services.
See the reference topic "OAuth 2.0 APIs for web server flow" for more information.
Authorized values:
  • bearer
  • basic
Output
Code Description
204
No Content. Indicates that the file folder was successfully deleted.
401
Unauthorized.
404
Not Found.
403
Forbidden. The server refuses to fulfill a request, typically because the request was for an object that you don't have permission to access.
In order to delete a Collection, the currently authenticated user must be the owner of the Collection, an administrator, or have been given Delete permission on the Collection. Delete permission is given through the Manager Role of a collection. To test whether the current user can delete a Collection, use the Get list of members of a specific role of a Collection to see if the user belongs to the Manager Role.
500
Internal server error. The server encountered an unexpected condition that prevented it from fulfilling the request.