List knowledge bases
Every knowledge base this client can manage. Accounts come from the token: if your credentials cover several, all of them are listed together and each row carries the accountId + instance pair that identifies its account. accountId and instance are optional filters — they narrow the result, never widen it. An account is named by the pair, not by accountId alone: the same accountId exists in more than one instance, so filtering on accountId by itself can return rows from several accounts, which may belong to different customers. Send both to address one account. listMyCloudChatAccounts returns each accountId together with its instance.
Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Query Parameters
Account to narrow to, e.g. 7. Not an account on its own: accountId is only unique within an instance, so sending it alone can match several accounts — possibly different customers — and all of them are listed. Pass instance alongside it to address exactly one account. Get the pair from listMyCloudChatAccounts. Omit both to list every account the credentials cover.
CloudChat instance the account lives in, e.g. 4. Pair it with accountId — the two together name exactly one account, while accountId alone does not. Get the pair from listMyCloudChatAccounts. On its own it narrows to every account the credentials cover in that instance.
Rows to skip. Page with total and hasNext from the response.
Page size. Capped at 200.
Field to order by.
kbName, createdAt, updatedAt Order direction.
asc, desc Response
One page of knowledge bases. Every row carries accountId and instance — the pair that identifies the account — so the rows stay attributable when the filter matched more than one account.
One page of knowledge bases.
The knowledge bases on this page.
Total matching the query, across all pages.
12
Offset this page started at.
0
Page size actually applied (capped at 200).
50
Whether another page follows.
false