aiWebSearchIsConfigured
Boolean aiWebSearchIsConfigured(entityId)
GET /api/2.0/ai/web-search/is-configured
Is configured
Tells whether web search is available in a scope, as a bare boolean, which is the cheap check for hiding or showing the feature. entityId picks a room and has to name one the caller can open. It reports the same state as GET api/2.0/ai/web-search/get-active-config without transferring the configuration itself. A true answer means a provider is stored, not that the provider is currently reachable - probe that with POST api/2.0/ai/web-search/test-connection.
Parameters
| Name | In | Type | Description | Notes |
|---|---|---|---|---|
| entityId | query | String | The DocSpace entity the request is scoped to - the room, folder or agent workspace the chat is invoked from. Omit for the portal-wide scope. | [optional] [example: 1234] |
Responses
| Status code | Description | Type | Response headers |
|---|---|---|---|
| 200 | Whether a web-search provider is stored for the scope. | Boolean | - |
| 400 | entityId is not a string. | AiErrorResponse | - |
| 401 | Missing asc_auth_key cookie or Authorization header. | AiErrorResponse | - |
| 403 | AI is disabled for this portal, the caller is a guest, or the room named by entityId is one the caller cannot open. Relayed from the DocSpace AI service or the Files API. | AiErrorResponse | - |
| 404 | The referenced object does not exist: an unknown or deleted room named by entityId, or an object the caller cannot read - for those the two cases are deliberately indistinguishable. | AiErrorResponse | - |
| 500 | Unhandled failure. The reason is logged server-side and never echoed back. | AiErrorResponse | - |
Return type
Boolean
Authorization
HTTP request headers
- Content-Type: Not defined
- Accept: application/json