GET /contents
endpoint of the Knowledge Editor API. The value for that parameter should be a string (“active“ or “inactive“).
externalId
field for contents. This is no longer possible. The externalId
field's purpose is to link a related instance's content to the main instance's content when the latter is created. Its value should therefore never be modified.
GET /contents
endpoint returns model phrases.
Attributes
endpoints.
Contents
endpoints. Instead of user IDs, these endpoints now return users' names and email addresses.
GET /contents/external/{externalId}
endpoint to retrieve contents from related instances based on their content ID in the primary instance.
DELETE /contents/{contentId}
endpoint to delete contents.
PATCH /contents/{contentId}
endpoint. This is now fixed, so users can edit content titles using the Knowledge Editor API, applying the same rules as they would using the Content Editor.
relatedContents
parameter to the POST /contents
and PATCH /contents/{id}
endpoints in the Knowledge Editor API to include related contents upon updating an existing content.
We updated the GET /contents
endpoint of the Knowledge API so that it includes the fields createdByName
, createdByEmail
, updatedByName
and updatedByEmail
.
New Feature: We added the new endpoint POST /drafts
that allows users to create content drafts.
POST /publication
that allows to publish programmatically an instance to Test and/or Production.
Added pagination in the GET /contents
endpoint. It now returns the length, offset and total number of contents within a pagination object.
PATCH /contents/{contentId}
endpoint allows to update objects in all attributes and user types.
POST /contents
and PATCH /contents/{contentId}
endpoints allow to modify publication and expiration dates per any user type
POST /contents/{contentId}/relatedContents
. This endpoint allows to relate contents programmatically.
DELETE /contents/{contentId}/relatedContents
. This endpoint allows to remove relations between contents programmatically.