You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In addition to the data sources that Glean has built-in support for, Glean also provides a REST API that enables customers to put arbitrary content in the search index. This is useful, for example, for doing permissions-aware search over content in internal tools that reside on-prem as well as for searching over applications that Glean does not currently support first class. In addition these APIs allow the customer to push organization data (people info, organization structure etc) into Glean.
@@ -23,7 +21,7 @@ info:
23
21
These API clients provide type-safe, idiomatic interfaces for working with Glean IndexingAPIs in your language of choice.
24
22
x-logo:
25
23
url: https://app.glean.com/images/glean-text2.svg
26
-
x-speakeasy-name: "Glean API"
24
+
x-speakeasy-name: 'Glean API'
27
25
servers:
28
26
- url: https://{instance}-be.glean.com
29
27
variables:
@@ -414,7 +412,7 @@ paths:
414
412
content:
415
413
application/json:
416
414
schema:
417
-
$ref: "#/components/schemas/ChatResponse"
415
+
$ref: '#/components/schemas/ChatResponse'
418
416
examples:
419
417
defaultExample:
420
418
value:
@@ -477,10 +475,10 @@ paths:
477
475
agent: DEFAULT
478
476
mode: DEFAULT
479
477
fragments:
480
-
- text: "**Reading:**"
478
+
- text: '**Reading:**'
481
479
- structuredResults:
482
480
- document:
483
-
id: "123"
481
+
id: '123'
484
482
title: Company Handbook
485
483
citationResponse:
486
484
value:
@@ -492,7 +490,7 @@ paths:
492
490
mode: DEFAULT
493
491
citations:
494
492
- sourceDocument:
495
-
id: "123"
493
+
id: '123'
496
494
title: Company Handbook
497
495
referenceRanges:
498
496
- textRange:
@@ -3179,7 +3177,7 @@ paths:
3179
3177
/rest/api/v1/governance/data/policies/{id}:
3180
3178
get:
3181
3179
description: Fetches the specified policy version, or the latest if no version is provided.
3182
-
summary: Gets specified Policy.
3180
+
summary: Gets specified policy
3183
3181
operationId: getpolicy
3184
3182
x-visibility: Public
3185
3183
tags:
@@ -3213,7 +3211,7 @@ paths:
3213
3211
x-speakeasy-name-override: retrieve
3214
3212
post:
3215
3213
description: Updates an existing policy.
3216
-
summary: Updates an existing policy.
3214
+
summary: Updates an existing policy
3217
3215
operationId: updatepolicy
3218
3216
tags:
3219
3217
- Governance
@@ -3246,7 +3244,7 @@ paths:
3246
3244
/rest/api/v1/governance/data/policies:
3247
3245
get:
3248
3246
description: Lists policies with filtering.
3249
-
summary: Lists policies.
3247
+
summary: Lists policies
3250
3248
operationId: listpolicies
3251
3249
x-visibility: Public
3252
3250
tags:
@@ -3279,7 +3277,7 @@ paths:
3279
3277
x-speakeasy-name-override: list
3280
3278
post:
3281
3279
description: Creates a new policy with specified specifications and returns its id.
description: Fetches the visibility override status of the documents passed.
3422
-
summary: Fetches documents visibility.
3420
+
summary: Fetches documents visibility
3423
3421
operationId: getdocvisibility
3424
3422
x-visibility: Public
3425
3423
tags:
@@ -3447,7 +3445,7 @@ paths:
3447
3445
x-speakeasy-name-override: list
3448
3446
post:
3449
3447
description: Sets the visibility-override state of the documents specified, effectively hiding or un-hiding documents.
3450
-
summary: Hide/Un-hide docs.
3448
+
summary: Hide or unhide docs
3451
3449
operationId: setdocvisibility
3452
3450
x-visibility: Public
3453
3451
tags:
@@ -7244,6 +7242,9 @@ components:
7244
7242
type: integer
7245
7243
description: Timeout in milliseconds for the request. A `408` error will be returned if handling the request takes longer.
7246
7244
example: 30000
7245
+
sessionInfo:
7246
+
description: Optional object for tracking the session used by the client and for debugging purposes.
7247
+
$ref: "#/components/schemas/SessionInfo"
7247
7248
applicationId:
7248
7249
type: string
7249
7250
description: The ID of the application this request originates from, used to determine the configuration of underlying chat processes. This should correspond to the ID set during admin setup. If not specified, the default chat experience will be used.
0 commit comments