Skip to main content

deleteRoomTags

FolderWrapper deleteRoomTags(id, BatchTagsRequestDto)

DELETE /api/2.0/files/rooms/{id}/tags

Detach tags from a room

Detaches the named tags from a room and returns the room with its remaining tag set. Only the link between the room and the tag is removed: the tag stays in the portal catalogue and keeps working for every other room, and DELETE api/2.0/files/tags is what removes it from the portal itself. Names that are not in the catalogue, or not attached to this room, are skipped without an error, so a successful answer does not prove that anything was detached; compare the returned tag set instead. An empty list is accepted and does nothing, while a null entry in the list is rejected as an invalid request. The caller must be a manager of the room or an administrator of the portal, and a room in the Archive section is refused with 403. A tag that loses its last room stays in the catalogue, and only deleting that room takes the tag with it.

Parameters​

NameInTypeDescriptionNotes
idpathInteger (int32)The room whose tags are changed, named by the identifier that GET api/2.0/files/rooms reports for it.[required] [example: 1]
BatchTagsRequestDtobodyBatchTagsRequestDtoThe names to attach or to detach.[optional]

Responses​

Status codeDescriptionTypeResponse headers
200The room with its tag set after the changeFolderWrapperX-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset
400The request body cannot be read or has no names, a name is null, blank or longer than 255 characters, or a third-party identifier refers to a storage account that is not connected--
403The caller may not edit this room, or the room is archived--
404The room does not exist, or the id is neither a 32-bit number nor a third-party identifier of a known storage type--
500A third-party identifier carries a storage account number beyond the 32-bit range--
401UnauthorizedErrorApiResponse-
429Too Many Requests.ErrorApiResponseRetry-After
502Bad Gateway. Returned by the reverse proxy, response body may be HTML and not JSON.--
503Service Unavailable. Returned by the reverse proxy, response body may be HTML and not JSON.--

Return type​

FolderWrapper

Third-party storage​

For a file or folder in a connected third-party storage the identifier is a string such as sbox-42, and the call differs in these parts only:

NameInTypeDescriptionNotes
idpathStringThe room whose tags are changed, named by the identifier that `GET api/2.0/files/rooms` reports for it.[required] [example: sbox-42]

Return type: ThirdPartyFolderWrapper

Authorization​

Basic, OAuth2 (scopes: read, write), ApiKeyBearer, asc_auth_key, Bearer, OpenId

HTTP request headers​

  • Content-Type: application/json
  • Accept: application/json