Create a Vocabulary Entry - Content REST API - Current - Current - Ready - Hyland Experience - external

Hyland Experience Content REST API

Platform
Hyland Experience
Product
Content REST API
Release
Current
License

Creates an entry for the specified vocabulary.

Base Request

POST /api/vocabularies/[sysvocab_id]

where [sysvocab_id] is the alphanumeric ID for the vocabulary.

Headers

Header Name Description Required Values
Authorization The access token Required Bearer [access_token]

where [access_token] is a string generated when you complete authentication (see Getting Started)

User-Agent Identity of the client making the request to the server Required [product]/[version]

where [product] is the name of the software you are using to make the request and [version] is the numbered version of the software (for example, MyCompanyProduct/1.0).

For information on other types of values commonly included in user-agent request headers, see the User-Agent HTTP header reference section on the Mozilla developer documentation website.

HXCS-REPOSITORY The repository ID Optional Any contributed repository name. Default is default.
Accept The format of the data to be returned Optional application/vnd.hxcs.v1+json
Content-Type The format of the data to be posted Optional application/json

Request Body

See Vocabulary for request body details. The request body follows the same structure as the response body.

Sample Request

POST /api/vocabularies/[sysvocab_id]

Authorization: Bearer [access_token]
User-Agent: MyCompanyProduct/1.0
HXCS-REPOSITORY: default
Accept: application/vnd.hxcs.v1+json
Content-Type: application/json

{
  "sysvocab_key": "string",
  "sysvocab_id": "string"
}

Response

See Vocabulary for response body details and a sample response.

Status Codes and Errors

The following table lists the returned status codes.

Code Description Notes
201 Created Returns the created vocabulary entry.
400 Bad Request The server could not process the request due to an invalid vocabulary entry key or label.
401 Not Authorized Authentication has failed or was not provided.
403 Not Allowed Access permissions are invalid or missing.
404 Not Found The vocabulary could not be found.
409 Conflict The request could not be processed because the created entry already exists in the specified vocabulary.