Update content source
Changes the fields you send and returns the full updated document.
Send only the fields you want to change, plus version with the num from your last read and a change_description. This is a JSON merge-patch: a field you leave out keeps its stored value, and every list or map you send replaces the stored one whole. The id goes in the URL; if you also send id in the body it must match.
Authentication
JWT bearer token authentication. Include the Configuration API key in the Authorization header as ‘Bearer <token>’.
Path parameters
The id of the content source, as returned when it was created or listed.
Request
Which containers in the source (for example knowledge bases, spaces, sites, drives, folders or categories) are ingested: all, only selected ones, or all except selected ones.
Users who have access to this content: all users, selected users, or no users. Defaults to no users on create.
Response
External system the content is ingested from, such as Box, Confluence, Google Drive, Jira, Outlook, SharePoint & OneDrive, Slack, ServiceNow, Unily, Zendesk or GitHub. Cannot be changed after creation.
Which containers in the source (for example knowledge bases, spaces, sites, drives, folders or categories) are ingested: all, only selected ones, or all except selected ones.
Users who have access to this content: all users, selected users, or no users. Defaults to no users on create.