npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@gleanwork/api-client

v0.17.3

Published

The Glean TypeScript SDK provides convenient access to the Glean REST API in both browser and Node.js environments. It offers full TypeScript types, modern async/await support, and uses the [fetch](https://developer.mozilla.org/en-US/docs/Web/API/Fetch_AP

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

vardhman-singhvardhman-singhtravis-hoover-gleantravis-hoover-gleantaozhou-gleantaozhou-gleandejim-juang-gleandejim-juang-gleancfreeman-gleancfreeman-gleanchenhao-yang-gleanchenhao-yang-gleannlfurniss-gleannlfurniss-gleansteve-calvert-gleansteve-calvert-gleanrwjblue-gleanrwjblue-gleandavid-hamilton-gleandavid-hamilton-glean

Keywords

Readme

Glean TypeScript API Client

The Glean TypeScript SDK provides convenient access to the Glean REST API in both browser and Node.js environments. It offers full TypeScript types, modern async/await support, and uses the fetch API under the hood.

Unified SDK Architecture

This SDK combines both the Client and Indexing API namespaces into a single unified package:

  • Client API: Used for search, retrieval, and end-user interactions with Glean content
  • Indexing API: Used for indexing content, permissions, and other administrative operations

Each namespace has its own authentication requirements and access patterns. While they serve different purposes, having them in a single SDK provides a consistent developer experience across all Glean API interactions.

// Example of accessing Client namespace
const glean = new Glean({
  serverURL: "https://mycompany-be.glean.com",
  apiToken: 'client-token'
});

await glean.client.search.query({ 
  query: 'search term' 
});

// Example of accessing Indexing namespace 
const glean = new Glean({
  serverURL: "https://mycompany-be.glean.com",
  apiToken: 'indexing-token'
});

await glean.indexing.documents.index({ 
  /* document data */ 
});

Remember that each namespace requires its own authentication token type as described in the Authentication Methods section.

Summary

Glean API: # Introduction 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.

Usage guidelines

This API is evolving fast. Glean will provide advance notice of any planned backwards incompatible changes along with a 6-month sunset period for anything that requires developers to adopt the new versions.

API Clients

Official API clients for the Glean Indexing API are available in multiple languages:

These API clients provide type-safe, idiomatic interfaces for working with Glean IndexingAPIs in your language of choice.

Table of Contents

SDK Installation

The SDK can be installed with either npm, pnpm, bun or yarn package managers.

NPM

npm add @gleanwork/api-client
# Install optional peer dependencies if you plan to use React hooks
npm add @tanstack/react-query react react-dom

PNPM

pnpm add @gleanwork/api-client
# Install optional peer dependencies if you plan to use React hooks
pnpm add @tanstack/react-query react react-dom

Bun

bun add @gleanwork/api-client
# Install optional peer dependencies if you plan to use React hooks
bun add @tanstack/react-query react react-dom

Yarn

yarn add @gleanwork/api-client
# Install optional peer dependencies if you plan to use React hooks
yarn add @tanstack/react-query react react-dom

[!NOTE] This package is published with CommonJS and ES Modules (ESM) support.

Requirements

For supported JavaScript runtimes, please consult RUNTIMES.md.

SDK Example Usage

Example 1

import { Glean } from "@gleanwork/api-client";

const glean = new Glean({
  apiToken: process.env["GLEAN_API_TOKEN"] ?? "",
});

async function run() {
  const result = await glean.client.chat.create({
    messages: [
      {
        fragments: [
          {
            text: "What are the company holidays this year?",
          },
        ],
      },
    ],
  });

  console.log(result);
}

run();

Example 2

import { Glean } from "@gleanwork/api-client";

const glean = new Glean({
  apiToken: process.env["GLEAN_API_TOKEN"] ?? "",
});

async function run() {
  const result = await glean.client.chat.createStream({
    messages: [
      {
        fragments: [
          {
            text: "What are the company holidays this year?",
          },
        ],
      },
    ],
  });

  console.log(result);
}

run();

Authentication

Per-Client Security Schemes

This SDK supports the following security scheme globally:

| Name | Type | Scheme | Environment Variable | | ---------- | ---- | ----------- | -------------------- | | apiToken | http | HTTP Bearer | GLEAN_API_TOKEN |

To authenticate with the API the apiToken parameter must be set when initializing the SDK client instance. For example:

import { Glean } from "@gleanwork/api-client";

const glean = new Glean({
  apiToken: process.env["GLEAN_API_TOKEN"] ?? "",
});

async function run() {
  const result = await glean.agents.search({
    name: "HR Policy Agent",
  });

  console.log(result);
}

run();

Authentication Methods

Glean supports different authentication methods depending on which API namespace you're using:

Client Namespace

The Client namespace supports two authentication methods:

  1. Manually Provisioned API Tokens

    • Can be created by an Admin or a user with the API Token Creator role
    • Used for server-to-server integrations

  2. OAuth

    • Requires OAuth setup to be completed by an Admin
    • Used for user-based authentication flows

Indexing Namespace

The Indexing namespace supports only one authentication method:

  1. Manually Provisioned API Tokens
    • Can be created by an Admin or a user with the API Token Creator role
    • Used for secure document indexing operations

[!IMPORTANT] Client tokens will not work for Indexing operations, and Indexing tokens will not work for Client operations. You must use the appropriate token type for the namespace you're accessing.

For more information on obtaining the appropriate token type, please contact your Glean administrator.

Available Resources and Operations

Agents

Client.Activity

Client.Agents

Client.Announcements

Client.Answers

Client.Authentication

Client.Chat

Client.Collections

Client.Datasources

Client.Documents

Client.Entities

Client.Governance.Data.Findings

  • create - Creates findings export
  • list - Lists findings exports
  • download - Downloads findings export
  • delete - Deletes findings export

Client.Governance.Data.Policies

  • retrieve - Gets specified policy
  • update - Updates an existing policy
  • list - Lists policies
  • create - Creates new policy
  • download - Downloads violations CSV for policy

Client.Governance.Data.Reports

  • create - Creates new one-time report
  • download - Downloads violations CSV for report
  • status - Fetches report run status

Client.Governance.Documents.Visibilityoverrides

  • list - Fetches documents visibility
  • create - Hide or unhide docs

Client.Insights

Client.Messages

Client.Pins

Client.Search

Client.Shortcuts

Client.Tools

Client.Verification

Indexing.Authentication

Indexing.CustomMetadata

Indexing.Datasource

  • status - Beta: Get datasource status

Indexing.Datasources

Indexing.Documents

Indexing.People

Indexing.Permissions

Indexing.Shortcuts

Search

Standalone functions

All the methods listed above are available as standalone functions. These functions are ideal for use in applications running in the browser, serverless runtimes or other environments where application bundle size is a primary concern. When using a bundler to build your application, all unused functionality will be either excluded from the final bundle or tree-shaken away.

To read more about standalone functions, check FUNCTIONS.md.

React hooks with TanStack Query

React hooks built on TanStack Query are included in this SDK. These hooks and the utility functions provided alongside them can be used to build rich applications that pull data from the API using one of the most popular asynchronous state management library.

To learn about this feature and how to get started, check REACT_QUERY.md.

[!WARNING]

This feature is currently in preview and is subject to breaking changes within the current major version of the SDK as we gather user feedback on it.

File uploads

Certain SDK methods accept files as part of a multi-part request. It is possible and typically recommended to upload files as a stream rather than reading the entire contents into memory. This avoids excessive memory consumption and potentially crashing with out-of-memory errors when working with very large files. The following example demonstrates how to attach a file stream to a request.

[!TIP]

Depending on your JavaScript runtime, there are convenient utilities that return a handle to a file without reading the entire contents into memory:

  • Node.js v20+: Since v20, Node.js comes with a native openAsBlob function in node:fs.
  • Bun: The native Bun.file function produces a file handle that can be used for streaming file uploads.
  • Browsers: All supported browsers return an instance to a File when reading the value from an <input type="file"> element.
  • Node.js v18: A file stream can be created using the fileFrom helper from fetch-blob/from.js.
import { Glean } from "@gleanwork/api-client";
import { openAsBlob } from "node:fs";

const glean = new Glean({
  apiToken: process.env["GLEAN_API_TOKEN"] ?? "",
});

async function run() {
  const result = await glean.client.chat.uploadFiles({
    files: [
      await openAsBlob("example.file"),
    ],
  });

  console.log(result);
}

run();

Retries

Some of the endpoints in this SDK support retries. If you use the SDK without any configuration, it will fall back to the default retry strategy provided by the API. However, the default retry strategy can be overridden on a per-operation basis, or across the entire SDK.

To change the default retry strategy for a single API call, simply provide a retryConfig object to the call:

import { Glean } from "@gleanwork/api-client";

const glean = new Glean({
  apiToken: process.env["GLEAN_API_TOKEN"] ?? "",
});

async function run() {
  const result = await glean.agents.search({
    name: "HR Policy Agent",
  }, {
    retries: {
      strategy: "backoff",
      backoff: {
        initialInterval: 1,
        maxInterval: 50,
        exponent: 1.1,
        maxElapsedTime: 100,
      },
      retryConnectionErrors: false,
    },
  });

  console.log(result);
}

run();

If you'd like to override the default retry strategy for all operations that support retries, you can provide a retryConfig at SDK initialization:

import { Glean } from "@gleanwork/api-client";

const glean = new Glean({
  retryConfig: {
    strategy: "backoff",
    backoff: {
      initialInterval: 1,
      maxInterval: 50,
      exponent: 1.1,
      maxElapsedTime: 100,
    },
    retryConnectionErrors: false,
  },
  apiToken: process.env["GLEAN_API_TOKEN"] ?? "",
});

async function run() {
  const result = await glean.agents.search({
    name: "HR Policy Agent",
  });

  console.log(result);
}

run();

Error Handling

The following errors may be thrown by the SDK:

| Status Code | Description | Error Type | Content Type | | ----------- | ----------------------- | ---------------------- | ---------------- | | 400 | Invalid Request | errors.GleanError | */* | | 401 | Not Authorized | errors.GleanError | */* | | 403 | Permission Denied | errors.GleanDataError | application/json | | 408 | Request Timeout | errors.GleanError | */* | | 422 | Invalid Query | errors.GleanDataError | application/json | | 429 | Too Many Requests | errors.GleanError | */* | | 4XX | Other Client Errors | errors.GleanError | */* | | 5XX | Internal Server Errors | errors.GleanError | */* |

Example

import { Glean } from "@gleanwork/api-client";****
import { GleanDataError, GleanError } from "glean/models/errors";

const glean = new Glean({
  apiToken: process.env["GLEAN_BEARER_AUTH"] ?? "",
});

try {
  const data = await glean.client.search.execute({
    query: "What are the company holidays this year?",
  });
  console.log(data);
} catch (error) {
  if (error instanceof GleanError) {
    console.error(error.message);
    console.error(error.statusCode);
    console.error(error.rawResponse);
    console.error(error.body);
  }

  // If the server returned structured data
  if (error instanceof GleanDataError) {
    console.error(error.errorMessages);
    console.error(error.invalidOperators);
  }

  throw error;
}

Advanced Error Handling

Validation errors can also occur when either method arguments or data returned from the server do not match the expected format. The SDKValidationError that is thrown as a result will capture the raw value that failed validation in an attribute called rawValue. Additionally, a pretty() method is available on this error that can be used to log a nicely formatted multi-line string since validation errors can list many issues and the plain error string may be difficult read when debugging.

In some rare cases, the SDK can fail to get a response from the server or even make the request due to unexpected circumstances such as network conditions. These types of errors are captured in the models/errors/httpclienterrors.ts module:

| HTTP Client Error | Description | | ---------------------------------------------------- | ---------------------------------------------------- | | RequestAbortedError | HTTP request was aborted by the client | | RequestTimeoutError | HTTP request timed out due to an AbortSignal signal | | ConnectionError | HTTP client was unable to make a request to a server | | InvalidRequestError | Any input used to create a request is invalid | | UnexpectedClientError | Unrecognised or unexpected error |

Server Selection

Server Variables

The default server https://{instance}-be.glean.com contains variables and is set to https://instance-name-be.glean.com by default. To override default values, the following parameters are available when initializing the SDK client instance:

| Variable | Parameter | Default | Description | | ---------- | ------------------ | ----------------- | ------------------------------------------------------------------------------------------------------ | | instance | instance: string | "instance-name" | The instance name (typically the email domain without the TLD) that determines the deployment backend. |

Example

import { Glean } from "@gleanwork/api-client";

const glean = new Glean({
  serverIdx: 0,
  instance: "instance-name",
  apiToken: process.env["GLEAN_API_TOKEN"] ?? "",
});

async function run() {
  const result = await glean.agents.search({
    name: "HR Policy Agent",
  });

  console.log(result);
}

run();

Override Server URL Per-Client

The default server can be overridden globally by passing a URL to the serverURL: string optional parameter when initializing the SDK client instance. For example:

import { Glean } from "@gleanwork/api-client";

const glean = new Glean({
  serverURL: "https://instance-name-be.glean.com",
  apiToken: process.env["GLEAN_API_TOKEN"] ?? "",
});

async function run() {
  const result = await glean.agents.search({
    name: "HR Policy Agent",
  });

  console.log(result);
}

run();

Override Server URL Per-Operation

The server URL can also be overridden on a per-operation basis, provided a server list was specified for the operation. For example:

import { Glean } from "@gleanwork/api-client";

const glean = new Glean({
  apiToken: process.env["GLEAN_API_TOKEN"] ?? "",
});

async function run() {
  const result = await glean.indexing.customMetadata.upsert(
    {
      customMetadata: [],
    },
    "<id>",
    "<value>",
    {
      serverURL: "https://instance-name-be.glean.com",
    },
  );

  console.log(result);
}

run();

Custom HTTP Client

The TypeScript SDK makes API calls using an HTTPClient that wraps the native Fetch API. This client is a thin wrapper around fetch and provides the ability to attach hooks around the request lifecycle that can be used to modify the request or handle errors and response.

The HTTPClient constructor takes an optional fetcher argument that can be used to integrate a third-party HTTP client or when writing tests to mock out the HTTP client and feed in fixtures.

The following example shows how to:

  • route requests through a proxy server using undici's ProxyAgent
  • use the "beforeRequest" hook to add a custom header and a timeout to requests
  • use the "requestError" hook to log errors
import { Glean } from "@gleanwork/api-client";
import { ProxyAgent } from "undici";
import { HTTPClient } from "@gleanwork/api-client/lib/http";

const dispatcher = new ProxyAgent("http://proxy.example.com:8080");

const httpClient = new HTTPClient({
  // 'fetcher' takes a function that has the same signature as native 'fetch'.
  fetcher: (input, init) =>
    // 'dispatcher' is specific to undici and not part of the standard Fetch API.
    fetch(input, { ...init, dispatcher } as RequestInit),
});

httpClient.addHook("beforeRequest", (request) => {
  const nextRequest = new Request(request, {
    signal: request.signal || AbortSignal.timeout(5000)
  });

  nextRequest.headers.set("x-custom-header", "custom value");

  return nextRequest;
});

httpClient.addHook("requestError", (error, request) => {
  console.group("Request Error");
  console.log("Reason:", `${error}`);
  console.log("Endpoint:", `${request.method} ${request.url}`);
  console.groupEnd();
});

const sdk = new Glean({ httpClient: httpClient });

Debugging

You can setup your SDK to emit debug logs for SDK requests and responses.

You can pass a logger that matches console's interface as an SDK option.

[!WARNING] Beware that debug logging will reveal secrets, like API tokens in headers, in log messages printed to a console or files. It's recommended to use this feature only during local development and not in production.

import { Glean } from "@gleanwork/api-client";

const sdk = new Glean({ debugLogger: console });

You can also enable a default debug logger by setting an environment variable GLEAN_DEBUG to true.

Experimental Features and Deprecation Testing

The SDK provides options to test upcoming API changes before they become the default behavior. This is useful for:

  • Testing experimental features before they are generally available
  • Preparing for deprecations by excluding deprecated endpoints ahead of their removal

Configuration Options

You can configure these options either via environment variables or SDK constructor options:

Using Environment Variables

// Set environment variables before initializing the SDK
process.env.X_GLEAN_EXCLUDE_DEPRECATED_AFTER = '2026-10-15';
process.env.X_GLEAN_INCLUDE_EXPERIMENTAL = 'true';

import { Glean } from "@gleanwork/api-client";

const glean = new Glean({
  apiToken: process.env["GLEAN_API_TOKEN"] ?? "",
  serverURL: "https://mycompany-be.glean.com",
});

Using SDK Constructor Options

import { Glean } from "@gleanwork/api-client";
import type { SDKOptions } from "@gleanwork/api-client";
import type { XGleanOptions } from "@gleanwork/api-client/hooks/x-glean-options.js";

const opts = {
  apiToken: process.env["GLEAN_API_TOKEN"] ?? "",
  serverURL: "https://mycompany-be.glean.com",
  excludeDeprecatedAfter: "2026-10-15",
  includeExperimental: true,
} satisfies SDKOptions & XGleanOptions;

const glean = new Glean(opts);

Option Reference

| Option | Environment Variable | Type | Description | | ------ | -------------------- | ---- | ----------- | | excludeDeprecatedAfter | X_GLEAN_EXCLUDE_DEPRECATED_AFTER | string (date) | Exclude API endpoints that will be deprecated after this date (format: YYYY-MM-DD). Use this to test your integration against upcoming deprecations. | | includeExperimental | X_GLEAN_INCLUDE_EXPERIMENTAL | boolean | When true, enables experimental API features that are not yet generally available.