- Portal Manager
- V4
- Subscribe to an Article
The Subscribe to an Article API allows eGain users, authenticated customers and agents to subscribe and receive notifications about changes to an Article.
- Notifications are sent only if the following conditions are met:
- The Article content has been modified since the last published version.
- The attachment list has been modified since the last published version.
- The author has checked the "Include Article in new and modified Article list" option while publishing the Article.
- For the Subscribe to an Article API to execute successfully:
- The Article must be in the portal.
- The user must have provided an email address.
- Agent Permissions: The following permissions are required if the user is an agent:
- If the Article has Access Tags:
- The Article must be available for the agent's current user profile.
- If the Article has Publish Views:
- At least one edition of the Article must be available for the agent's current user profile.
- If the Article has filters and the "tags query parameter" is provided:
- The Article filters must match the provided tags or tag groups.
- If the Article has Access Tags:
- Customer Permissions: The following permissions are required if the user is a customer:
- If the Article has Access Tags:
- The portal must have a default user profile
- The Article must be available for the portal's default user profile.
- If the Article has Publish Views:
- The portal must have a default user profile
- At least one edition must be available for the portal's default user profile.
- If the Article has filters and the "tags query parameter" is provided, then the Article filters must match the provided tags or tag groups.
- If the Article has Access Tags:
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.
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.
- oAuthUser
- oAuthOnBehalfOfUser
- oAuthCustomer
- oAuthOnBehalfOfCustomer
curl -i -X PUT \
https://api.egain.cloud/knowledge/portalmgr/v4/portals/PROD-1000/articles/PROD-2996/subscribe \
-H 'Accept-Language: en-US' \
-H 'Authorization: Bearer <YOUR_TOKEN_HERE>' \
-H 'x-egain-activity-id: 59237' \
-H 'x-ext-integration-id: 3155180e-0c13-43e9-9c38-e9045bcbf176' \
-H 'x-ext-interaction-id: 3155180e-0c13-43e9-9c38-e9045bcbf176'