Knowledge Base

Gets list of KB

get

This endpoint is used to fetch all the active KB's for the current organization

Authorizations
AuthorizationstringRequired
Query parameters
items_per_pageintegerOptional

Number of results to return per page.

offsetintegerOptional

The initial index from which to return the results.

Responses
chevron-right
200Success
application/json
get
/ux/common/kb/kb/
200Success

Creates a new KB

post

This endpoint is used to save a new KB for the current organization

Authorizations
AuthorizationstringRequired
Body
Other propertiesanyOptional
Responses
chevron-right
200Success
application/json
Responseany
post
/ux/common/kb/kb/

Gets a kb with the given id

get

This endpoint is used to fetch a kb details in the current organization

Authorizations
AuthorizationstringRequired
Path parameters
idstringRequired
Responses
chevron-right
200Success
application/json
Responseany
get
/ux/common/kb/kb/{id}/
200Success

No content

Edits the kb with given id

put

This endpoint is used to edit an existing KB for the current organization

Authorizations
AuthorizationstringRequired
Path parameters
idstringRequired
Body

Serializer for Documents.

Recognized primitve fields:

* ``StringField``
* ``URLField``
* ``EmailField``
* ``IntField``
* ``LongField``
* ``FloatField``
* ``DecimalField``
* ``BooleanField``
* ``DateTimeField``
* ``ComplexDateTimeField``
* ``ObjectIdField``
* ``SequenceField`` (assumes it has integer counter)
* ``UUIDField``
* ``GeoPointField``
* ``GeoJsonBaseField`` (all those fields)
* ``DateField``

Compound fields: ListField and DictField are mapped to corresponding DRF fields, with respect to nested field specification.

The ReferenceField is handled like ForeignKey in DRF: there nested serializer autogenerated if serializer depth greater then 0, otherwise it's handled by it's own (results as str(id)).

For EmbeddedDocumentField also nested serializer autogenerated for non-zero depth, otherwise it is skipped. TODO: THIS IS PROBABLY WRONG AND SHOULD BE FIXED.

Generic fields GenericReferenceField and GenericEmbeddedDocumentField are handled by their own with corresponding serializer fields.

Not well supported or untested:

``FileField``
``ImageField``
``BinaryField``

All other fields are mapped to DocumentField and probably will work wrong.

kb_idstring · max: 25Required
titlestringRead-onlyRequired
contentstringRead-onlyRequired
creation_timestringRead-onlyRequired
kbtypestringRead-onlyRequired
created_bystring | nullableOptional
keywordsstringRead-onlyRequired
faqsstringRead-onlyRequired
known_errorstringRead-onlyRequired
imagestringRead-onlyRequired
ratingstringRead-onlyRequired
likesstringRead-onlyRequired
viewsstringRead-onlyRequired
bookmarksstringRead-onlyRequired
user_likedstringRead-onlyRequired
rating_countstringRead-onlyRequired
is_bookmarkedstringRead-onlyRequired
commentsstringRead-onlyRequired
last_update_timestringRead-onlyRequired
is_updatedstringRead-onlyRequired
creatorinteger | nullableOptional
display_idstring · max: 50Optional
notify_usersstringRead-onlyRequired
Responses
chevron-right
200Success
application/json
put
/ux/common/kb/kb/{id}/
200Success

Deletes the KB with given id

delete

This endpoint is used to delete an existing KB for the current organization

Authorizations
AuthorizationstringRequired
Path parameters
idstringRequired
Responses
chevron-right
200Success
application/json
Responseany
delete
/ux/common/kb/kb/{id}/

No content

patch

API endpoint for knowledge base

Authorizations
AuthorizationstringRequired
Path parameters
idstringRequired
Body

Serializer for Documents.

Recognized primitve fields:

* ``StringField``
* ``URLField``
* ``EmailField``
* ``IntField``
* ``LongField``
* ``FloatField``
* ``DecimalField``
* ``BooleanField``
* ``DateTimeField``
* ``ComplexDateTimeField``
* ``ObjectIdField``
* ``SequenceField`` (assumes it has integer counter)
* ``UUIDField``
* ``GeoPointField``
* ``GeoJsonBaseField`` (all those fields)
* ``DateField``

Compound fields: ListField and DictField are mapped to corresponding DRF fields, with respect to nested field specification.

The ReferenceField is handled like ForeignKey in DRF: there nested serializer autogenerated if serializer depth greater then 0, otherwise it's handled by it's own (results as str(id)).

For EmbeddedDocumentField also nested serializer autogenerated for non-zero depth, otherwise it is skipped. TODO: THIS IS PROBABLY WRONG AND SHOULD BE FIXED.

Generic fields GenericReferenceField and GenericEmbeddedDocumentField are handled by their own with corresponding serializer fields.

Not well supported or untested:

``FileField``
``ImageField``
``BinaryField``

All other fields are mapped to DocumentField and probably will work wrong.

kb_idstring · max: 25Optional
titlestringRead-onlyOptional
contentstringRead-onlyOptional
creation_timestringRead-onlyOptional
kbtypestringRead-onlyOptional
created_bystring | nullableOptional
keywordsstringRead-onlyOptional
faqsstringRead-onlyOptional
known_errorstringRead-onlyOptional
imagestringRead-onlyOptional
ratingstringRead-onlyOptional
likesstringRead-onlyOptional
viewsstringRead-onlyOptional
bookmarksstringRead-onlyOptional
user_likedstringRead-onlyOptional
rating_countstringRead-onlyOptional
is_bookmarkedstringRead-onlyOptional
commentsstringRead-onlyOptional
last_update_timestringRead-onlyOptional
is_updatedstringRead-onlyOptional
creatorinteger | nullableOptional
display_idstring · max: 50Optional
notify_usersstringRead-onlyOptional
Responses
chevron-right
200Success
application/json
patch
/ux/common/kb/kb/{id}/
200Success

Add attachments for the selected kb.

post

This endpoint is used to add new attachments.

Authorizations
AuthorizationstringRequired
Body

Serializer for Documents.

Recognized primitve fields:

* ``StringField``
* ``URLField``
* ``EmailField``
* ``IntField``
* ``LongField``
* ``FloatField``
* ``DecimalField``
* ``BooleanField``
* ``DateTimeField``
* ``ComplexDateTimeField``
* ``ObjectIdField``
* ``SequenceField`` (assumes it has integer counter)
* ``UUIDField``
* ``GeoPointField``
* ``GeoJsonBaseField`` (all those fields)
* ``DateField``

Compound fields: ListField and DictField are mapped to corresponding DRF fields, with respect to nested field specification.

The ReferenceField is handled like ForeignKey in DRF: there nested serializer autogenerated if serializer depth greater then 0, otherwise it's handled by it's own (results as str(id)).

For EmbeddedDocumentField also nested serializer autogenerated for non-zero depth, otherwise it is skipped. TODO: THIS IS PROBABLY WRONG AND SHOULD BE FIXED.

Generic fields GenericReferenceField and GenericEmbeddedDocumentField are handled by their own with corresponding serializer fields.

Not well supported or untested:

``FileField``
``ImageField``
``BinaryField``

All other fields are mapped to DocumentField and probably will work wrong.

kb_idstring · max: 25Required
titlestringRead-onlyRequired
contentstringRead-onlyRequired
creation_timestringRead-onlyRequired
kbtypestringRead-onlyRequired
created_bystring | nullableOptional
keywordsstringRead-onlyRequired
faqsstringRead-onlyRequired
known_errorstringRead-onlyRequired
imagestringRead-onlyRequired
ratingstringRead-onlyRequired
likesstringRead-onlyRequired
viewsstringRead-onlyRequired
bookmarksstringRead-onlyRequired
user_likedstringRead-onlyRequired
rating_countstringRead-onlyRequired
is_bookmarkedstringRead-onlyRequired
commentsstringRead-onlyRequired
last_update_timestringRead-onlyRequired
is_updatedstringRead-onlyRequired
creatorinteger | nullableOptional
display_idstring · max: 50Optional
notify_usersstringRead-onlyRequired
Responses
chevron-right
200Success
application/json
post
/ux/common/kb/kb/add-attachment/
200Success

Gets attachments for the selected kb.

get

This endpoint is used to fetch the attachments.

Authorizations
AuthorizationstringRequired
Responses
chevron-right
200Success
application/json
get
/ux/common/kb/kb/attachment/
200Success

Get the bookmarked KB's

get

This endpoint is used to get the bookmarked KB's

Authorizations
AuthorizationstringRequired
Responses
chevron-right
200Success
application/json
get
/ux/common/kb/kb/bookmarks/
200Success

Get the categories for the KB

get

This endpoint is used to get the categories

Authorizations
AuthorizationstringRequired
Responses
chevron-right
200Success
application/json
get
/ux/common/kb/kb/categories/
200Success

Save the comment for a KB

post

This endpoint is used to save the comment for a KB

Authorizations
AuthorizationstringRequired
Body

Serializer for Documents.

Recognized primitve fields:

* ``StringField``
* ``URLField``
* ``EmailField``
* ``IntField``
* ``LongField``
* ``FloatField``
* ``DecimalField``
* ``BooleanField``
* ``DateTimeField``
* ``ComplexDateTimeField``
* ``ObjectIdField``
* ``SequenceField`` (assumes it has integer counter)
* ``UUIDField``
* ``GeoPointField``
* ``GeoJsonBaseField`` (all those fields)
* ``DateField``

Compound fields: ListField and DictField are mapped to corresponding DRF fields, with respect to nested field specification.

The ReferenceField is handled like ForeignKey in DRF: there nested serializer autogenerated if serializer depth greater then 0, otherwise it's handled by it's own (results as str(id)).

For EmbeddedDocumentField also nested serializer autogenerated for non-zero depth, otherwise it is skipped. TODO: THIS IS PROBABLY WRONG AND SHOULD BE FIXED.

Generic fields GenericReferenceField and GenericEmbeddedDocumentField are handled by their own with corresponding serializer fields.

Not well supported or untested:

``FileField``
``ImageField``
``BinaryField``

All other fields are mapped to DocumentField and probably will work wrong.

kb_idstring · max: 25Required
titlestringRead-onlyRequired
contentstringRead-onlyRequired
creation_timestringRead-onlyRequired
kbtypestringRead-onlyRequired
created_bystring | nullableOptional
keywordsstringRead-onlyRequired
faqsstringRead-onlyRequired
known_errorstringRead-onlyRequired
imagestringRead-onlyRequired
ratingstringRead-onlyRequired
likesstringRead-onlyRequired
viewsstringRead-onlyRequired
bookmarksstringRead-onlyRequired
user_likedstringRead-onlyRequired
rating_countstringRead-onlyRequired
is_bookmarkedstringRead-onlyRequired
commentsstringRead-onlyRequired
last_update_timestringRead-onlyRequired
is_updatedstringRead-onlyRequired
creatorinteger | nullableOptional
display_idstring · max: 50Optional
notify_usersstringRead-onlyRequired
Responses
chevron-right
200Success
application/json
post
/ux/common/kb/kb/comment/
200Success

Get the comments for a KB

get

This endpoint is used to get the comments for KB

Authorizations
AuthorizationstringRequired
Responses
chevron-right
200Success
application/json
get
/ux/common/kb/kb/comments/
200Success
put

API endpoint for knowledge base

Authorizations
AuthorizationstringRequired
Path parameters
idstringRequired
Body

Serializer for Documents.

Recognized primitve fields:

* ``StringField``
* ``URLField``
* ``EmailField``
* ``IntField``
* ``LongField``
* ``FloatField``
* ``DecimalField``
* ``BooleanField``
* ``DateTimeField``
* ``ComplexDateTimeField``
* ``ObjectIdField``
* ``SequenceField`` (assumes it has integer counter)
* ``UUIDField``
* ``GeoPointField``
* ``GeoJsonBaseField`` (all those fields)
* ``DateField``

Compound fields: ListField and DictField are mapped to corresponding DRF fields, with respect to nested field specification.

The ReferenceField is handled like ForeignKey in DRF: there nested serializer autogenerated if serializer depth greater then 0, otherwise it's handled by it's own (results as str(id)).

For EmbeddedDocumentField also nested serializer autogenerated for non-zero depth, otherwise it is skipped. TODO: THIS IS PROBABLY WRONG AND SHOULD BE FIXED.

Generic fields GenericReferenceField and GenericEmbeddedDocumentField are handled by their own with corresponding serializer fields.

Not well supported or untested:

``FileField``
``ImageField``
``BinaryField``

All other fields are mapped to DocumentField and probably will work wrong.

kb_idstring · max: 25Required
titlestringRead-onlyRequired
contentstringRead-onlyRequired
creation_timestringRead-onlyRequired
kbtypestringRead-onlyRequired
created_bystring | nullableOptional
keywordsstringRead-onlyRequired
faqsstringRead-onlyRequired
known_errorstringRead-onlyRequired
imagestringRead-onlyRequired
ratingstringRead-onlyRequired
likesstringRead-onlyRequired
viewsstringRead-onlyRequired
bookmarksstringRead-onlyRequired
user_likedstringRead-onlyRequired
rating_countstringRead-onlyRequired
is_bookmarkedstringRead-onlyRequired
commentsstringRead-onlyRequired
last_update_timestringRead-onlyRequired
is_updatedstringRead-onlyRequired
creatorinteger | nullableOptional
display_idstring · max: 50Optional
notify_usersstringRead-onlyRequired
Responses
chevron-right
200Success
application/json
put
/ux/common/kb/kb/delete-attachment/{id}/
200Success

Save the feedback for a KB

post

This endpoint is used to save feedback for a KB

Authorizations
AuthorizationstringRequired
Body

Serializer for Documents.

Recognized primitve fields:

* ``StringField``
* ``URLField``
* ``EmailField``
* ``IntField``
* ``LongField``
* ``FloatField``
* ``DecimalField``
* ``BooleanField``
* ``DateTimeField``
* ``ComplexDateTimeField``
* ``ObjectIdField``
* ``SequenceField`` (assumes it has integer counter)
* ``UUIDField``
* ``GeoPointField``
* ``GeoJsonBaseField`` (all those fields)
* ``DateField``

Compound fields: ListField and DictField are mapped to corresponding DRF fields, with respect to nested field specification.

The ReferenceField is handled like ForeignKey in DRF: there nested serializer autogenerated if serializer depth greater then 0, otherwise it's handled by it's own (results as str(id)).

For EmbeddedDocumentField also nested serializer autogenerated for non-zero depth, otherwise it is skipped. TODO: THIS IS PROBABLY WRONG AND SHOULD BE FIXED.

Generic fields GenericReferenceField and GenericEmbeddedDocumentField are handled by their own with corresponding serializer fields.

Not well supported or untested:

``FileField``
``ImageField``
``BinaryField``

All other fields are mapped to DocumentField and probably will work wrong.

kb_idstring · max: 25Required
titlestringRead-onlyRequired
contentstringRead-onlyRequired
creation_timestringRead-onlyRequired
kbtypestringRead-onlyRequired
created_bystring | nullableOptional
keywordsstringRead-onlyRequired
faqsstringRead-onlyRequired
known_errorstringRead-onlyRequired
imagestringRead-onlyRequired
ratingstringRead-onlyRequired
likesstringRead-onlyRequired
viewsstringRead-onlyRequired
bookmarksstringRead-onlyRequired
user_likedstringRead-onlyRequired
rating_countstringRead-onlyRequired
is_bookmarkedstringRead-onlyRequired
commentsstringRead-onlyRequired
last_update_timestringRead-onlyRequired
is_updatedstringRead-onlyRequired
creatorinteger | nullableOptional
display_idstring · max: 50Optional
notify_usersstringRead-onlyRequired
Responses
chevron-right
200Success
application/json
post
/ux/common/kb/kb/feedback/
200Success

Gets history for the selected kb.

get

This endpoint is used to fetch the history.

Authorizations
AuthorizationstringRequired
Responses
chevron-right
200Success
application/json
get
/ux/common/kb/kb/history/
200Success

Get the options for the KB configuration

get

This endpoint is used to get the default options for KB config

Authorizations
AuthorizationstringRequired
Responses
chevron-right
200Success
application/json
get
/ux/common/kb/kb/options/
200Success

Get the ratings for the KB

get

This endpoint is used to get the ratings for KB

Authorizations
AuthorizationstringRequired
Responses
chevron-right
200Success
application/json
get
/ux/common/kb/kb/ratings/
200Success

Get the recent KB's

get

This endpoint is used to get the recent KB's

Authorizations
AuthorizationstringRequired
Responses
chevron-right
200Success
application/json
get
/ux/common/kb/kb/recent/
200Success
get

This endpoint is used to get the related KB's

Authorizations
AuthorizationstringRequired
Responses
chevron-right
200Success
application/json
get
/ux/common/kb/kb/related/
200Success

Get user list

get

This endpoint is used to get the user list from team

Authorizations
AuthorizationstringRequired
Responses
chevron-right
200Success
application/json
get
/ux/common/kb/kb/team_user_map/
200Success
get

Function will return user info dict :param request: request. :return: dict

Authorizations
AuthorizationstringRequired
Responses
chevron-right
200Success
application/json
get
/ux/common/kb/kb/user-list/
200Success

Get the viewers for the KB

get

This endpoint is used to get the viewers for a KB

Authorizations
AuthorizationstringRequired
Responses
chevron-right
200Success
application/json
get
/ux/common/kb/kb/viewers/
200Success

Get the view count for the KB

get

This endpoint is used to get the view count for a KB

Authorizations
AuthorizationstringRequired
Responses
chevron-right
200Success
application/json
get
/ux/common/kb/kb/views/
200Success

Last updated