Documentation

{{docApp.title}}

{{docApp.description}}

Connect an AI assistant

Your AI assistant can read this documentation directly, so it answers from the current content instead of guessing. Add one of the servers below to your client — they use the Model Context Protocol (MCP). Each one covers a different body of content, so add the one you need.

The catalog did not load. Refresh the page to try again.

Loading…

How can we help?

{{docApp.searchError}}

Searching in {{docApp.searchFilterBySpecificBookTitle}}

 {{docApp.currentResultsSearchText}}  in {{docApp.searchFilterBySpecificBookTitle}}
Found {{docApp.searchResponse.totalResultsAvailable}} matches. Showing the top {{docApp.searchResponse.results ? docApp.searchResponse.results.length : 0}}. Use a more specific search to further narrow down the results.
No documentation pages match this search, so all content types are shown. Most matches are in {{docApp.searchDocTypeRescue.best.name}}.
There is no book with the ID "{{docApp.searchBookRescue.bid}}", so the book filter from this link was ignored and results from all books are shown.

You have an odd number of " characters in your search terms - each one needs closing with a matching " character!
  • {{resultItem.title}} {{resultItem.matchedBy === 'semantic' ? 'semantic' : (resultItem.matchedBy === 'both' ? 'keyword + semantic' : 'keyword')}}

    {{resultItem.url}}

{{docApp.libraryHomeViewProduct.title || docApp.libraryHomeViewProduct.id}}

{{docApp.libraryHomeViewProduct.description}}

  1. {{book.title}}

Application API / chatbotKnowledgeSearch

Operation Information

  • Application Reference: com.hornbill.servicemanager
  • Scope: Global
  • Class: Application
  • Required Privilege Level: user
  • Required Rights: Group H - executeSystemAPIs

Description

This operation is responsible for querying various entities via chatbot integrations, and returns relevant search results

Request Parameters

The chatbotKnowledgeSearch API takes the following input parameters.

Note

When sending a JSON request payload to the API, the order of parameters is not significant. However, for XML request payloads, parameters must be provided in the exact order specified in this documentation to comply with input validation requirements.

Name Type Required Description
entities xs:string Yes Array of Entities to Search against i.e. ["Faqs", "KnowledgeBaseArticles", "PublishedRequests","Requests"]
userId xs:string Yes ID of the user to search against
searchQuery xs:string Yes The User's Search Query
serviceId xs:string No The service ID
site xs:string No The site
category xs:string No The category
rowStart xs:integer Yes Used for paginating the results
limit xs:integer Yes Used for paginating the results
getCount xs:boolean No If true, then returns the total number of results
getData xs:boolean No If true, then returns the results
openRequestsOnly xs:boolean No If true, then returns the open requests only

Response Parameters

Name Type Description
searchResults xs:string List of results
totalSearchResults xs:string The total count of the results
exceptionName xs:string The name of the exception, if any exception occurs
exceptionDescription xs:string The description of the exception, if any exception occurs

Code Examples

In This Document