Knowledge
List knowledge source providers
List the registered providers a knowledge source can be connected through — key, label, declared modes, declared source configuration and the kinds each delivers. Requires knowledge:manage and credentials:use.
GET
List knowledge source providers
The reference panel describes the current v3 operation. The notes below describe its v2 compatibility API. Follow the v3 request schema for current calls: v3 can move identifiers from the body or query into the URL. Keep the v2 method, path, and payload together when using the compatibility API.
v2 compatibility notes
GET /api/v2/knowledge/synchronized-sources/listProviders lists the registered synchronized_knowledge providers, ordered by label: the providerKey that Connect a knowledge source takes, its label, the modes it declares, the source configuration it declares and the kinds it delivers. It never returns a connection, vendor or credential detail. MCP hosts call it through forge_call_operation with operationId listSynchronizedSourceProviders.
It needs both knowledge:manage and credentials:use, the pair connecting a source requires, and the credential’s scopes must reach both. A credential missing either answers 403 permission_denied naming it, recorded. The route takes no query parameter but limit and cursor; any other answers 400 bad_request.
The response is { data: [{ providerKey, label, modes, sourceConfig?, provides }], meta }: every registered provider is returned, in one response without limit, or in pages of limit with cursor. A deployment with no registered provider answers an empty list.
modes accepts only synchronize, the supported mode. The Console uses it automatically; records are copied in on a schedule. Connecting a source in a retired mode answers 400 bad_request.
sourceConfig, when the provider declares one, is what a source of it takes: itsfields(the onlyconfigkeyscreateSourceaccepts for it, each with itslabel,help,typeofstring,numberorselect, and whether it isrequired), itscontainer(whatexternalContainerIdnames, and whether the provider lists them),curatedApplicable,recommendedIntervalMinutes, andderivedKeys, the settings a sync derives and no caller may set. A provider without one takes free-form non-secret settings.provideslists the kinds of record the provider delivers: eachkind, itsdisplayName, whether it issearchable, and itssensitiveAttributes, which are kept out of search.
externalContainerId and no config: its account is derived from the freshservice/helpdesk credential on the first sync.
Authorizations
Query Parameters
Response
Knowledge source providers

