跳到主要内容

createRoomTag

StringWrapper createRoomTag(CreateTagRequestDto)

POST /api/2.0/files/tags

Create a room tag

Adds a custom tag to the portal-wide catalog of room tags and answers with the stored name. Tags are shared by the whole portal instead of belonging to the caller: once the tag exists, every room manager can attach it to their own rooms with PUT api/2.0/files/rooms/{id}/tags, and that call also creates a tag it does not find. Creating a name that is already in the catalog returns the existing tag unchanged rather than a duplicate or an error, so repeating the call after a timeout is safe. A blank name, or one longer than the published limit, is rejected as an invalid request. Only a room manager or a portal administrator may create a tag, and a user or a guest is refused. The answer is the name as stored, and that name is the value to send in the tags filter of GET api/2.0/files/rooms and in the room tag calls. The catalog itself is read with GET api/2.0/files/tags.

Parameters​

NameInTypeDescriptionNotes
CreateTagRequestDtobodyCreateTagRequestDto[optional]

Responses​

Status codeDescriptionTypeResponse headers
200The name of the created tag, or of the tag that already carried this nameStringWrapperX-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset
400The request body cannot be read or has no name, or the name is empty, blank or longer than 255 characters--
403Only a room manager or a portal administrator can create tags--
401UnauthorizedErrorApiResponse-
429Too Many Requests.ErrorApiResponseRetry-After
500Internal Server Error.ErrorApiResponse-
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​

StringWrapper

Authorization​

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

HTTP request headers​

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