Skip to content
/ pipeshub-sdk-typescript Public

pipeshub-sdk is the official typescript client library for integrating Pipeshub into your product and internal tools

pipeshub.com/

License

Apache-2.0 license
0 stars 2 forks Branches Tags Activity
Star
Notifications You must be signed in to change notification settings

pipeshub-ai/pipeshub-sdk-typescript

BranchesTags

Repository files navigation

pipeshub-sdk-typescript

Summary

PipesHub API: Unified API documentation for PipesHub services.

PipesHub is an enterprise-grade platform providing:

  • User authentication and management
  • Document storage and version control
  • Knowledge base management
  • Enterprise search and conversational AI
  • Third-party integrations via connectors
  • System configuration management
  • Crawling job scheduling
  • Email services

Authentication

Most endpoints require JWT Bearer token authentication. Some internal endpoints use scoped tokens for service-to-service communication.

Base URLs

All endpoints use the /api/v1 prefix unless otherwise noted.

Table of Contents

SDK Installation

Tip

To finish publishing your SDK to npm and others you must run your first generation action.

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

NPM

npm add <UNSET>

PNPM

pnpm add <UNSET>

Bun

bun add <UNSET>

Yarn

yarn add <UNSET>

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

import { Pipeshub } from "pipeshub";

const pipeshub = new Pipeshub({
  serverURL: "https://api.example.com",
});

async function run() {
  const result = await pipeshub.userAccount.initializeAuth({
    email: "user@example.com",
  });

  console.log(result);
}

run();

Authentication

Per-Client Security Schemes

This SDK supports the following security scheme globally:

Name Type Scheme Environment Variable
bearerAuth http HTTP Bearer PIPESHUB_BEARER_AUTH

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

import { Pipeshub } from "pipeshub";

const pipeshub = new Pipeshub({
  serverURL: "https://api.example.com",
  bearerAuth: process.env["PIPESHUB_BEARER_AUTH"] ?? "",
});

async function run() {
  const result = await pipeshub.userAccount.initializeAuth({
    email: "user@example.com",
  });

  console.log(result);
}

run();

Per-Operation Security Schemes

Some operations in this SDK require the security scheme to be specified at the request level. For example:

import { Pipeshub } from "pipeshub";

const pipeshub = new Pipeshub({
  serverURL: "https://api.example.com",
});

async function run() {
  const result = await pipeshub.userAccount.resetPasswordWithToken({
    scopedToken: process.env["PIPESHUB_SCOPED_TOKEN"] ?? "",
  }, {
    password: "H9GEHoL829GXj06",
  });

  console.log(result);
}

run();

Available Resources and Operations

Available methods

AgentConversations

  • list - List agent conversations
  • start - Create agent conversation
  • stream - Create agent conversation with streaming
  • get - Get agent conversation
  • delete - Delete agent conversation
  • addMessage - Add message to agent conversation
  • streamMessage - Add message with streaming
  • regenerate - Regenerate agent response

Agents

AgentTemplates

  • list - List agent templates
  • create - Create agent template
  • get - Get agent template
  • update - Update agent template
  • delete - Delete agent template

AiModelsConfiguration

  • create - Bulk create AI models configuration
  • getAll - Get all AI models configuration

AiModelsProviders

AuthConfig

AuthenticationConfiguration

AuthenticationConfigurations

Connector

ConnectorConfiguration

  • get - Get connector configuration
  • update - Update connector configuration
  • updateFiltersSync - Update filters and sync configuration

ConnectorConfigurations

ConnectorControl

  • toggle - Toggle connector sync or agent

ConnectorFilters

ConnectorInstances

ConnectorOAuth

ConnectorOauthConfiguration

ConnectorOAuthConfiguration

ConnectorOAuthConfigurations

ConnectorRegistry

  • list - List available connector types
  • getSchema - Get connector configuration schema

ConnectorService

ConnectorServices

Conversations

CrawlingJobs

  • schedule - Schedule a crawling job
  • getStatus - Get crawling job status
  • remove - Remove a crawling job
  • pause - Pause a crawling job
  • resume - Resume a paused crawling job
  • list - Get all crawling job statuses
  • removeAll - Remove all crawling jobs

DoclingService

  • healthCheck - [Docling Service] Health check
  • processPdf - [Docling Service] Process PDF document
  • parsePdf - [Docling Service] Parse PDF (Phase 1)
  • createBlocks - [Docling Service] Create blocks from parse result (Phase 2)

DocumentBuffer

  • get - Get document buffer
  • update - Update document buffer

DocumentManagement

DocumentUpload

EmailOperations

  • send - Send a transactional email

Folders

IndexingService

  • health - [Indexing Service] Health check

KnowledgeBases

MailConfiguration

MetricsCollection

MetricsCollections

  • toggle - Enable or disable metrics collection

Oauth

  • exchangeCode - Exchange OAuth authorization code for tokens

OauthApps

OauthConfiguration

  • getRegistry - List OAuth-capable connector types
  • list - List OAuth configurations
  • listConfigsByType - List OAuth configs for connector type
  • get - Get OAuth configuration
  • update - Update OAuth configuration

OAuthConfiguration

  • create - Create OAuth configuration

OauthConfigurations

OauthProvider

OpenIDConnect

OrganizationAuthConfig

OrganizationAuthConfigs

  • create - Create organization authentication configuration

OrganizationAuthConfiguration

Organizations

Permissions

  • grant - Grant permissions
  • list - List permissions
  • update - Update permissions
  • remove - Remove permissions

PlatformSettings

PublicUrls

QueryService

  • search - [Query Service] Semantic search
  • chat - [Query Service] Chat with knowledge base
  • chatStream - [Query Service] Streaming chat with knowledge base
  • healthCheck - [Query Service] AI model health check
  • listTools - [Query Service] List available agent tools

QueryServices

QueueManagement

Records

  • get - Get all records across knowledge bases
  • list - Get records for a knowledge base
  • getById - Get record by ID
  • update - Update record
  • delete - Delete record
  • streamContent - Stream record content
  • move - Move a record to another folder

Saml

SemanticSearch

SmtpConfiguration

StorageConfiguration

Teams

Upload

UserAccount

UserGroups

Users

VersionControl

Webhooks

  • verifyGmail - [Connector Service] Gmail webhook verification
  • postGmail - [Connector Service] Gmail webhook
  • handle - [Connector Service] Google Workspace Admin webhook

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.

Available standalone functions

Server-sent event streaming

Server-sent events are used to stream content from certain operations. These operations will expose the stream as an async iterable that can be consumed using a for await...of loop. The loop will terminate when the server no longer has any events to send and closes the underlying connection.

import { Pipeshub } from "pipeshub";

const pipeshub = new Pipeshub({
  serverURL: "https://api.example.com",
  bearerAuth: process.env["PIPESHUB_BEARER_AUTH"] ?? "",
});

async function run() {
  const result = await pipeshub.conversations.stream({
    query: "What are the key findings from our Q4 financial report?",
    recordIds: [
      "507f1f77bcf86cd799439011",
      "507f1f77bcf86cd799439012",
    ],
    modelKey: "gpt-4-turbo",
    modelName: "GPT-4 Turbo",
    chatMode: "balanced",
  });

  for await (const event of result) {
    console.log(event);
  }
}

run();

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 { openAsBlob } from "node:fs";
import { Pipeshub } from "pipeshub";

const pipeshub = new Pipeshub({
  serverURL: "https://api.example.com",
  bearerAuth: process.env["PIPESHUB_BEARER_AUTH"] ?? "",
});

async function run() {
  const result = await pipeshub.users.uploadDisplayPicture({
    file: 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 { Pipeshub } from "pipeshub";

const pipeshub = new Pipeshub({
  serverURL: "https://api.example.com",
});

async function run() {
  const result = await pipeshub.userAccount.initializeAuth({
    email: "user@example.com",
  }, {
    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 { Pipeshub } from "pipeshub";

const pipeshub = new Pipeshub({
  serverURL: "https://api.example.com",
  retryConfig: {
    strategy: "backoff",
    backoff: {
      initialInterval: 1,
      maxInterval: 50,
      exponent: 1.1,
      maxElapsedTime: 100,
    },
    retryConnectionErrors: false,
  },
});

async function run() {
  const result = await pipeshub.userAccount.initializeAuth({
    email: "user@example.com",
  });

  console.log(result);
}

run();

Error Handling

PipeshubError is the base class for all HTTP error responses. It has the following properties:

Property Type Description
error.message string Error message
error.statusCode number HTTP response status code eg 404
error.headers Headers HTTP response headers
error.body string HTTP body. Can be empty string if no body is returned.
error.rawResponse Response Raw HTTP response
error.data$ Optional. Some errors may contain structured data. See Error Classes.

Example

import { Pipeshub } from "pipeshub";
import * as errors from "pipeshub/models/errors";

const pipeshub = new Pipeshub({
  serverURL: "https://api.example.com",
});

async function run() {
  try {
    const result = await pipeshub.userAccount.initializeAuth({
      email: "user@example.com",
    });

    console.log(result);
  } catch (error) {
    // The base class for HTTP error responses
    if (error instanceof errors.PipeshubError) {
      console.log(error.message);
      console.log(error.statusCode);
      console.log(error.body);
      console.log(error.headers);

      // Depending on the method different errors may be thrown
      if (error instanceof errors.AuthError) {
        console.log(error.data$.error); // string
        console.log(error.data$.message); // string
        console.log(error.data$.code); // string
        console.log(error.data$.statusCode); // number
      }
    }
  }
}

run();

Error Classes

Primary error:

Less common errors (13)

Network errors:

Inherit from PipeshubError:

  • AuthError: Authentication error response with details for debugging and user feedback.

    Common Error Codes:
    • INVALID_CREDENTIALS - Wrong password or OTP
    • ACCOUNT_BLOCKED - Account locked after 5 failed attempts
    • SESSION_EXPIRED - Session token has expired
    • OTP_EXPIRED - OTP code has expired (10 min validity)
    • USER_NOT_FOUND - Email not registered
    • INVALID_TOKEN - JWT token is invalid or malformed
    • METHOD_NOT_ALLOWED - Auth method not enabled for org
    . Applicable to 10 of 286 methods.*
  • OAuthErrorResponse: OAuth 2.0 Error Response (RFC 6749 Section 5.2). Standard error format for OAuth endpoints. Applicable to 5 of 286 methods.*
  • BadRequestError: Bad request. Possible reasons:
    • SMTP not configured properly (missing host, port, or fromEmail)
    • Invalid or unknown email template type
    • Missing required templateData fields for the selected template
    • Invalid email format in sendEmailTo or sendCcTo
    . Status code 400. Applicable to 1 of 286 methods.*
  • NotFoundError: SMTP configuration not found in application config. Status code 404. Applicable to 1 of 286 methods.*
  • SendEmailInternalServerError: Internal server error. Email sending failed due to:
    • SMTP server connection failure
    • Authentication failure with SMTP server
    • Template compilation error
    • Network issues
    . Status code 500. Applicable to 1 of 286 methods.*
  • FailError: Service is unhealthy or dependency check failed. Status code 500. Applicable to 1 of 286 methods.*
  • QueryServiceHealthCheckInternalServerError: Model health check failed. Status code 500. Applicable to 1 of 286 methods.*
  • ResponseValidationError: Type mismatch between the data returned from the server and the structure expected by the SDK. See error.rawValue for the raw value and error.pretty() for a nicely formatted multi-line string.

* Check the method documentation to see if the error is applicable.

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 { Pipeshub } from "pipeshub";
import { ProxyAgent } from "undici";
import { HTTPClient } from "pipeshub/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 Pipeshub({ 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 { Pipeshub } from "pipeshub";

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

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

About

pipeshub-sdk is the official typescript client library for integrating Pipeshub into your product and internal tools

pipeshub.com/

Topics

sdk pipeshub-sdk

Resources

Readme

License

Apache-2.0 license

Contributing

Contributing
Activity
Custom properties

Stars

0 stars

Watchers

0 watching

Forks

2 forks
Report repository

Releases

No releases published

Packages

No packages published

Languages