Skip to content

Knowledge Portal Manager APIs

License

The following licenses are required to use the Knowledge Access APIs:

  • If the user is an agent, then the Knowledge + AI license is required.
  • If the user is a customer, the Self-Service and Advanced Self-Service licenses must be available.

Tiers

TierTier NameNamed UsersDescription
Tier 1StarterUp to 10Designed for small-scale implementations or pilot environments
Tier 2GrowthUp to 1000Suitable for mid-scale deployments requiring moderate scalability
Tier 3EnterpriseGreater than 1000Supports large-scale environments with extended configuration options

API Resource Limits

The following Resources have predefined limits for specific access attributes for Starter, Growth and Enterprise use.

ResourceLimitsStarterGrowthEnterprise
Article ReferenceNumber of attachments used in any article255050
Number of custom attributes in an article102550
Number of publish views used in an article version202020
Topic ReferenceUser-defined topics in a department1000500050000
Depth of topics52020
Topics at any level50025002500
Number of custom attributes in a topic101010
Portal ReferenceTag categories in a portal151515
Topics to be included in a portal1005005000
Number of articles to display in announcements102525
Usage links and link groups setup for a portal51025
Download OpenAPI description
Languages
Servers
Production Server
https://api.egain.cloud/knowledge/portalmgr/v4

Article

Article APIs

Operations

Article Lists

Article List APIs

Operations

Bookmark

Bookmark APIs

Operations

Guided Help

Guided Help APIs

Operations

Portal

Portal API

Operations

Suggestion

Suggestion APIs

Operations

Topic

Topic APIs

Operations

User Details

User Details APIs

Operations

User Milestones

User Milestones APIs

Operations

User Profile

UserProfile APIs

Operations

Federated Search Event

Federated Search Event API

Operations

Connectors Search Events

Connectors Search Event APIs

Operations

Event for Search Using Connectors

Request

Overview

The Event for Search Using Connectors API creates an event to initiate a search operation for retrieving content from external sources or integrations within the portal. It allows users to set up search events based on specified criteria.

Security
oAuthUser(Required scopes:
https://api.egain.cloud/auth/kno...
)
or oAuthOnBehalfOfUser(Required scopes:
https://api.egain.cloud/auth/kno...
)
or oAuthCustomer(Required scopes:
https://api.egain.cloud/auth/kno...
)
or oAuthOnBehalfOfCustomer(Required scopes:
https://api.egain.cloud/auth/kno...
)
or oAuthAnonymousCustomer(Required scopes:
https://api.egain.cloud/auth/kno...
)
Path
portalIDstring[ 7 .. 20 ] characters^[a-zA-Z0-9]{2,4}-\d{4,15}$required

The ID of the portal being accessed.

A portal ID is composed of a 2-4 letter prefix, followed by a dash and 4-15 digits.

Example: PROD-1000
Headers
Content-Typestringrequired

The media type sent by the client.

Default application/json
Value"application/json"
Accept-Languagestringrequired

The Language locale accepted by the client (used for locale specific fields in resource representation and in error responses).

Enum"en-US""es-ES""fr-FR""it-IT""de-DE""nl-NL""pt-BR""pt-PT""da-DK""ru-RU"
Example: en-US
x-ext-integration-idstring<= 40 characters^[\w\W]+$

The unique numeric identifier for a tenant, used in self-service functionality as well as third-party integrations.

Note: The x-ext-integration-id and x-ext-interaction-id headers must always be provided together and cannot be supplied independently.

The x-egain-activity-id may be provided on its own, or it may be provided along with both x-ext-integration-id and x-ext-interaction-id.

Examples:
3155180e-0c13-43e9-9c38-e9045bcbf176
00Dbn00000IxGnx
x-egain-activity-idstring[ 4 .. 9 ] characters^[0-9]{4,9}$

A unique numeric interaction identifier from eGain.

Example: 59237
x-ext-interaction-idstring<= 40 characters^[\w\W]+$

A unique interaction identifier from other CRM applications.

Note: The x-ext-integration-id and x-ext-interaction-id headers must always be provided together and cannot be supplied independently.

The x-egain-activity-id may be provided on its own, or it may be provided along with both x-ext-integration-id and x-ext-interaction-id.

Examples:
3155180e-0c13-43e9-9c38-e9045bcbf176
00Dbn00000IxGnx
Bodyapplication/jsonrequired
languageCodestring(KbLanguageCode)required

A short language code. A list of codes can be found below:

CodeDescription
en-USEnglish (United States)
en-GBEnglish (United Kingdom)
fr-FRFrench (France)
es-ESSpanish (Spain)
it-ITItalian (Italy)
de-DEGerman (Germany)
nl-NLDutch (Netherlands)
pt-BRPortuguese (Brazil)
pt-PTPortuguese (Portugal)
da-DKDanish (Denmark)
sv-SESwedish (Sweden)
ru-RURussian (Russia)
fr-CAFrench (Canada)
zh-CNChinese (Simplified, China)
ja-JPJapanese (Japan)
ko-KRKorean (South Korea)
nn-NONorwegian Nynorsk (Norway)
Enum"en-US""en-GB""fr-FR""es-ES""it-IT""de-DE""nl-NL""pt-BR""pt-PT""da-DK"
qstring[ 1 .. 1024 ] charactersrequired

The string to use for the search.

Example: "India"
numberOfSearchResultsinteger(int32)[ 1 .. 25 ]required
Example: 10
curl -i -X POST \
  https://api.egain.cloud/knowledge/portalmgr/v4/portals/PROD-1000/search/connectors/event \
  -H 'Accept-Language: en-US' \
  -H 'Authorization: Bearer <YOUR_TOKEN_HERE>' \
  -H 'Content-Type: application/json' \
  -H 'x-egain-activity-id: 59237' \
  -H 'x-ext-integration-id: string' \
  -H 'x-ext-interaction-id: string' \
  -d '{
    "languageCode": "en-US",
    "q": "India",
    "numberOfSearchResults": 10
  }'

Responses

No Content

Response
No content

Event for Viewed Search Results Using Connectors

Request

Overview

The Event for Viewed Search Results Using Connectors API creates an event to log when search results from external content are viewed. This helps in tracking and analyzing user interactions with search results retrieved from various external sources.

Security
oAuthUser(Required scopes:
https://api.egain.cloud/auth/kno...
)
or oAuthOnBehalfOfUser(Required scopes:
https://api.egain.cloud/auth/kno...
)
or oAuthCustomer(Required scopes:
https://api.egain.cloud/auth/kno...
)
or oAuthOnBehalfOfCustomer(Required scopes:
https://api.egain.cloud/auth/kno...
)
or oAuthAnonymousCustomer(Required scopes:
https://api.egain.cloud/auth/kno...
)
Path
portalIDstring[ 7 .. 20 ] characters^[a-zA-Z0-9]{2,4}-\d{4,15}$required

The ID of the portal being accessed.

A portal ID is composed of a 2-4 letter prefix, followed by a dash and 4-15 digits.

Example: PROD-1000
Headers
Content-Typestringrequired

The media type sent by the client.

Default application/json
Value"application/json"
Accept-Languagestringrequired

The Language locale accepted by the client (used for locale specific fields in resource representation and in error responses).

Enum"en-US""es-ES""fr-FR""it-IT""de-DE""nl-NL""pt-BR""pt-PT""da-DK""ru-RU"
Example: en-US
x-ext-integration-idstring<= 40 characters^[\w\W]+$

The unique numeric identifier for a tenant, used in self-service functionality as well as third-party integrations.

Note: The x-ext-integration-id and x-ext-interaction-id headers must always be provided together and cannot be supplied independently.

The x-egain-activity-id may be provided on its own, or it may be provided along with both x-ext-integration-id and x-ext-interaction-id.

Examples:
3155180e-0c13-43e9-9c38-e9045bcbf176
00Dbn00000IxGnx
x-egain-activity-idstring[ 4 .. 9 ] characters^[0-9]{4,9}$

A unique numeric interaction identifier from eGain.

Example: 59237
x-ext-interaction-idstring<= 40 characters^[\w\W]+$

A unique interaction identifier from other CRM applications.

Note: The x-ext-integration-id and x-ext-interaction-id headers must always be provided together and cannot be supplied independently.

The x-egain-activity-id may be provided on its own, or it may be provided along with both x-ext-integration-id and x-ext-interaction-id.

Examples:
3155180e-0c13-43e9-9c38-e9045bcbf176
00Dbn00000IxGnx
Bodyapplication/jsonrequired
languageCodestring(KbLanguageCode)required

A short language code. A list of codes can be found below:

CodeDescription
en-USEnglish (United States)
en-GBEnglish (United Kingdom)
fr-FRFrench (France)
es-ESSpanish (Spain)
it-ITItalian (Italy)
de-DEGerman (Germany)
nl-NLDutch (Netherlands)
pt-BRPortuguese (Brazil)
pt-PTPortuguese (Portugal)
da-DKDanish (Denmark)
sv-SESwedish (Sweden)
ru-RURussian (Russia)
fr-CAFrench (Canada)
zh-CNChinese (Simplified, China)
ja-JPJapanese (Japan)
ko-KRKorean (South Korea)
nn-NONorwegian Nynorsk (Norway)
Enum"en-US""en-GB""fr-FR""es-ES""it-IT""de-DE""nl-NL""pt-BR""pt-PT""da-DK"
qstring[ 1 .. 1024 ] characters^[\w\W]+$required

The string to use for the search.

Example: "India"
urlstring[ 10 .. 2000 ] characters^(https?|ftp):\/\/([a-zA-Z0-9-]+\.)+[a-zA-Z]{...required

The URL of the search result.

Example: "https://egain.com/"
titlestring[ 1 .. 255 ] characters^[\w\W]+$required

The title of the search result.

Example: "Welcome to India"
curl -i -X POST \
  https://api.egain.cloud/knowledge/portalmgr/v4/portals/PROD-1000/view/searchresults/connectors/event \
  -H 'Accept-Language: en-US' \
  -H 'Authorization: Bearer <YOUR_TOKEN_HERE>' \
  -H 'Content-Type: application/json' \
  -H 'x-egain-activity-id: 59237' \
  -H 'x-ext-integration-id: string' \
  -H 'x-ext-interaction-id: string' \
  -d '{
    "languageCode": "en-US",
    "q": "India",
    "url": "https://beetle.egain.com/",
    "title": "Welcome to India"
  }'

Responses

No Content

Response
No content

Attachment

Attachment Upload API

Operations

Export

Content Export APIs

Operations