BasisTheory TypeScript Library


The BasisTheory TypeScript library provides convenient access to the BasisTheory APIs from TypeScript.

Table of Contents

- Documentation
- Installation
- Reference
- Usage
- Request and Response Types
- Exception Handling
- Pagination
- Advanced
- Additional Headers
- Additional Query String Parameters
- Retries
- Timeouts
- Aborting Requests
- Access Raw Response Data
- Runtime Compatibility
- Contributing
- File Uploads
- Binary Response

Documentation

API reference documentation is available here.

Installation

``sh
npm i -s @basis-theory/node-sdk
`

Reference

A full reference for this library is available here.

Usage

Instantiate and use the client with the following:

`typescript
import { BasisTheoryClient } from "@basis-theory/node-sdk";

const client = new BasisTheoryClient({ apiKey: "YOUR_API_KEY", correlationId: "YOUR_CORRELATION_ID" });
await client.tenants.self.get();
`

Request and Response Types

The SDK exports all request and response types as TypeScript interfaces. Simply import them with the
following namespace:

`typescript
import { BasisTheory } from "@basis-theory/node-sdk";

const request: BasisTheory.ApplicationsListRequest = {
...
};
`

Exception Handling

When the API returns a non-success status code (4xx or 5xx response), a subclass of the following error
will be thrown.

`typescript
import { BasisTheoryError } from "@basis-theory/node-sdk";

try {
await client.tenants.self.get(...);
} catch (err) {
if (err instanceof BasisTheoryError) {
console.log(err.statusCode);
console.log(err.message);
console.log(err.body);
console.log(err.rawResponse);
}
}
`

Pagination

List endpoints are paginated. The SDK provides an iterator so that you can simply loop over the items:

`typescript
import { BasisTheoryClient } from "@basis-theory/node-sdk";

const client = new BasisTheoryClient({ apiKey: "YOUR_API_KEY", correlationId: "YOUR_CORRELATION_ID" });
const response = await client.applications.list();
for await (const item of response) {
console.log(item);
}

// Or you can manually iterate page-by-page
let page = await client.applications.list();
while (page.hasNextPage()) {
page = page.getNextPage();
}
`

Advanced

$3

If you would like to send additional headers as part of the request, use the headers request option.

`typescript
const response = await client.tenants.self.get(..., {
headers: {
'X-Custom-Header': 'custom value'
}
});
`

$3

If you would like to send additional query string parameters as part of the request, use the queryParams request option.

`typescript
const response = await client.tenants.self.get(..., {
queryParams: {
'customQueryParamKey': 'custom query param value'
}
});
`

$3

The SDK is instrumented with automatic retries with exponential backoff. A request will be retried as long
as the request is deemed retryable and the number of retry attempts has not grown larger than the configured
retry limit (default: 2).

A request is deemed retryable when any of the following HTTP status codes is returned:

- 408 (Timeout)
- 429 (Too Many Requests)
- 5XX (Internal Server Errors)

Use the maxRetries request option to configure this behavior.

`typescript
const response = await client.tenants.self.get(..., {
maxRetries: 0 // override maxRetries at the request level
});
`

$3

The SDK defaults to a 60 second timeout. Use the timeoutInSeconds option to configure this behavior.

`typescript
const response = await client.tenants.self.get(..., {
timeoutInSeconds: 30 // override timeout to 30s
});
`

$3

The SDK allows users to abort requests at any point by passing in an abort signal.

`typescript
const controller = new AbortController();
const response = await client.tenants.self.get(..., {
abortSignal: controller.signal
});
controller.abort(); // aborts the request
`

$3

The SDK provides access to raw response data, including headers, through the .withRawResponse() method.
The .withRawResponse() method returns a promise that results to an object with a data and a rawResponse property.

`typescript
const { data, rawResponse } = await client.tenants.self.get(...).withRawResponse();

console.log(data);
console.log(rawResponse.headers['X-My-Header']);
`

$3


The SDK works in the following runtimes:

- Node.js 18+
- Vercel
- Cloudflare Workers
- Deno v1.25+
- Bun 1.0+
- React Native

$3

The SDK provides a way for you to customize the underlying HTTP client / Fetch function. If you're running in an
unsupported environment, this provides a way for you to break glass and ensure the SDK works.

`typescript
import { BasisTheoryClient } from "@basis-theory/node-sdk";

const client = new BasisTheoryClient({
...
fetcher: // provide your implementation here
});
`

Contributing

While we value open-source contributions to this SDK, this library is generated programmatically.
Additions made directly to this library would have to be moved over to our generation code,
otherwise they would be overwritten upon the next generated release. Feel free to open a PR as
a proof of concept, but know that we will not be able to merge it as-is. We suggest opening
an issue first to discuss with us!

On the other hand, contributions to the README are always very welcome!


File Uploads

You can upload files using the client:

`typescript
import { createReadStream } from "fs";
import { BasisTheoryClient } from "@basis-theory/node-sdk";

const client = new BasisTheoryClient({ apiKey: "YOUR_API_KEY", correlationId: "YOUR_CORRELATION_ID" });
await client.documents.upload({});
`
The client accepts a variety of types for file upload parameters:
* Stream types: fs.ReadStream, stream.Readable, and ReadableStream
* Buffered types: Buffer, Blob, File, ArrayBuffer, ArrayBufferView, and Uint8Array

$3

You can configure metadata when uploading a file:
`typescript
const file: Uploadable.WithMetadata = {
data: createReadStream("path/to/file"),
filename: "my-file", // optional
contentType: "audio/mpeg", // optional
contentLength: 1949, // optional
};
`

Alternatively, you can upload a file directly from a file path:
`typescript
const file : Uploadable.FromPath = {
path: "path/to/file",
filename: "my-file", // optional
contentType: "audio/mpeg", // optional
contentLength: 1949, // optional
};
`

The metadata is used to set the Content-Length, Content-Type, and Content-Disposition headers. If not provided, the client will attempt to determine them automatically.
For example, fs.ReadStream has a path property which the SDK uses to retrieve the file size from the filesystem without loading it into memory.

Binary Response

You can consume binary data from endpoints using the BinaryResponse type which lets you choose how to consume the data:

`typescript
const response = await client.documents.data.get(...);
const stream: ReadableStream = response.stream();
// const arrayBuffer: ArrayBuffer = await response.arrayBuffer();
// const blob: Blob = response.blob();
// const bytes: Uint8Array = response.bytes();
// You can only use the response body once, so you must choose one of the above methods.
// If you want to check if the response body has been used, you can use the following property.
const bodyUsed = response.bodyUsed;
`