Knowledge
List the containers a knowledge source could read
List, by label, the containers in a provider’s system that a new knowledge source at a writable target could read, checked as connecting a source is. Requires knowledge:manage and credentials:use.
POST
List the containers a new knowledge source could read
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
POST /api/v2/knowledge/synchronized-sources/listContainers lists, by label, the containers in a provider’s system that a new source at the target could read, for example the workspaces of a Freshservice account. Pass one container’s id as externalContainerId to Connect a knowledge source. It is the Console’s add-source container picker. MCP hosts call it through forge_call_operation with operationId listSynchronizedSourceContainers.
It needs both knowledge:manage and credentials:use, the pair connecting a source requires: the provider is asked with the credential on its vendor’s connection that resolves along the target scope, never one the request names. A credential missing either answers 403 permission_denied naming it, recorded.
The body is the Console picker’s arguments:
providerKey: a provider from List source providers whosesourceConfig.container.optionsFromislistContainers;targetScopeTypeand, for every type exceptcompany,targetScopeEntityId: the scope the new source would write to;config(optional): the provider’s non-secret settings, ascreateSourcetakes them.
- a target outside the caller’s writable namespaces answers the same recorded
403 forbiddenthatcreateSourceanswers; - an unregistered provider, or one that does not list its containers, answers
400 bad_request.
{ data: [{ id, label }], meta }, sorted by label, paged with limit and cursor. At most 1,000 containers are returned, and meta.partial is true when the listing reached that bound; its last page then answers meta.hasMore: false with meta.truncated: true. A container never carries a URL, key or vendor body.
When the provider cannot list, the answer names only its bounded code:
409 conflictwithSOURCE_CREDENTIAL_UNAVAILABLEwhen no approved credential resolves along the target scope (connect one, then retry), orLIST_CONTAINERS_UNSUPPORTED;500 internal_errorwith the code (for exampleLIST_CONTAINERS_FAILED) and therequestIdwhen the provider failed.
Idempotency-Key.
Authorizations
Query Parameters
Body
application/json
The source a container is wanted for: a registered provider that lists its containers (its sourceConfig.container.optionsFrom is listContainers in synchronized-sources/listProviders), and the scope the source would write to, which must be in the caller's writable namespaces. config holds the provider's non-secret settings, as createSynchronizedSource takes them.
Response
The containers, by label

