​
SDK Installation

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

​
NPM

npm add @abbyy-sdk/document-ai

​
PNPM

pnpm add @abbyy-sdk/document-ai

​
Bun

bun add @abbyy-sdk/document-ai

​
Yarn

yarn add @abbyy-sdk/document-ai zod

# Note that Yarn does not install peer dependencies automatically. You will need
# to install zod as shown above.

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

​
Requirements

​
Supported JavaScript runtimes

This SDK is intended to be used in JavaScript runtimes that support ECMAScript 2020 or newer. The SDK uses the following features:

Runtime environments that are explicitly supported are:

  • Evergreen browsers which include: Chrome, Safari, Edge, Firefox
  • Node.js active and maintenance LTS releases
    • Currently, this is v18 and v20
  • Bun v1 and above
  • Deno v1.39
    • Note that Deno does not currently have native support for streaming file uploads backed by the filesystem (issue link)

The following tsconfig.json options are recommended for projects using this SDK in order to get static type support for features like async iterables, streams and fetch-related APIs (for await...of, AbortSignal, Request, Response and so on):

{
  "compilerOptions": {
    "target": "es2020", // or higher
    "lib": ["es2020", "dom", "dom.iterable"],
  }
}

While target can be set to older ECMAScript versions, it may result in extra, unnecessary compatibility code being generated if you are not targeting old runtimes.

​
SDK Example Usage

​
Example

import { DocumentAi } from "@abbyy-sdk/document-ai";

const documentAi = new DocumentAi({
  apiKeyAuth: process.env["DOCUMENTAI_API_KEY_AUTH"] ?? "",
});

async function run() {
  const result = await documentAi.documents.list({
    cursor: "<optional_pagination_cursor_goes_here>",
  });

  for await (const page of result) {
    // Handle the page
    console.log(page);
  }
}

run();

​
Authentication

​
Per-Client Security Schemes

This SDK supports the following security scheme globally:

NameTypeSchemeEnvironment Variable
apiKeyAuthhttpHTTP BearerDOCUMENTAI_API_KEY_AUTH

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

import { DocumentAi } from "@abbyy-sdk/document-ai";

const documentAi = new DocumentAi({
  apiKeyAuth: process.env["DOCUMENTAI_API_KEY_AUTH"] ?? "",
});

async function run() {
  const result = await documentAi.documents.list({
    cursor: "<optional_pagination_cursor_goes_here>",
  });

  for await (const page of result) {
    // Handle the page
    console.log(page);
  }
}

run();

​
Available Resources and Operations

The available API operations and SDK implementation examples can be found within our API Reference documentation

​
Pagination

Some of the endpoints in this SDK support pagination. To use pagination, you make your SDK calls as usual, but the returned response object will also be an async iterable that can be consumed using the for await...of syntax.

Here’s an example of one such pagination call:

import { DocumentAi } from "@abbyy-sdk/document-ai";

const documentAi = new DocumentAi({
  apiKeyAuth: process.env["DOCUMENTAI_API_KEY_AUTH"] ?? "",
});

async function run() {
  const result = await documentAi.documents.list({
    cursor: "<optional_pagination_cursor_goes_here>",
  });

  for await (const page of result) {
    // Handle the page
    console.log(page);
  }
}

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 { DocumentAi } from "@abbyy-sdk/document-ai";

const documentAi = new DocumentAi({
  apiKeyAuth: process.env["DOCUMENTAI_API_KEY_AUTH"] ?? "",
});

async function run() {
  const result = await documentAi.documents.list({
    cursor: "<optional_pagination_cursor_goes_here>",
  }, {
    retries: {
      strategy: "backoff",
      backoff: {
        initialInterval: 1,
        maxInterval: 50,
        exponent: 1.1,
        maxElapsedTime: 100,
      },
      retryConnectionErrors: false,
    },
  });

  for await (const page of result) {
    // Handle the page
    console.log(page);
  }
}

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 { DocumentAi } from "@abbyy-sdk/document-ai";

const documentAi = new DocumentAi({
  retryConfig: {
    strategy: "backoff",
    backoff: {
      initialInterval: 1,
      maxInterval: 50,
      exponent: 1.1,
      maxElapsedTime: 100,
    },
    retryConnectionErrors: false,
  },
  apiKeyAuth: process.env["DOCUMENTAI_API_KEY_AUTH"] ?? "",
});

async function run() {
  const result = await documentAi.documents.list({
    cursor: "<optional_pagination_cursor_goes_here>",
  });

  for await (const page of result) {
    // Handle the page
    console.log(page);
  }
}

run();

​
Error Handling

Some methods specify known errors which can be thrown. All the known errors are enumerated in the models/errors/errors.ts module. The known errors for a method are documented under the Errors tables in SDK docs. For example, the list method may throw the following errors:

Error TypeStatus CodeContent Type
errors.BadRequestError400application/json
errors.UnauthorizedError401application/json
errors.TooManyRequestsError429application/json
errors.InternalServerError500application/json
errors.APIError4XX, 5XX*/*

If the method throws an error and it is not captured by the known errors, it will default to throwing a APIError.

import { DocumentAi } from "@abbyy-sdk/document-ai";
import {
  BadRequestError,
  InternalServerError,
  SDKValidationError,
  TooManyRequestsError,
  UnauthorizedError,
} from "@abbyy-sdk/document-ai/models/errors";

const documentAi = new DocumentAi({
  apiKeyAuth: process.env["DOCUMENTAI_API_KEY_AUTH"] ?? "",
});

async function run() {
  let result;
  try {
    result = await documentAi.documents.list({
      cursor: "<optional_pagination_cursor_goes_here>",
    });

    for await (const page of result) {
      // Handle the page
      console.log(page);
    }
  } catch (err) {
    switch (true) {
      // The server response does not match the expected SDK schema
      case (err instanceof SDKValidationError): {
        // Pretty-print will provide a human-readable multi-line error message
        console.error(err.pretty());
        // Raw value may also be inspected
        console.error(err.rawValue);
        return;
      }
      case (err instanceof BadRequestError): {
        // Handle err.data$: BadRequestErrorData
        console.error(err);
        return;
      }
      case (err instanceof UnauthorizedError): {
        // Handle err.data$: UnauthorizedErrorData
        console.error(err);
        return;
      }
      case (err instanceof TooManyRequestsError): {
        // Handle err.data$: TooManyRequestsErrorData
        console.error(err);
        return;
      }
      case (err instanceof InternalServerError): {
        // Handle err.data$: InternalServerErrorData
        console.error(err);
        return;
      }
      default: {
        // Other errors such as network errors, see HTTPClientErrors for more details
        throw err;
      }
    }
  }
}

run();

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 ErrorDescription
RequestAbortedErrorHTTP request was aborted by the client
RequestTimeoutErrorHTTP request timed out due to an AbortSignal signal
ConnectionErrorHTTP client was unable to make a request to a server
InvalidRequestErrorAny input used to create a request is invalid
UnexpectedClientErrorUnrecognised or unexpected error

​
Server Selection

​
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 { DocumentAi } from "@abbyy-sdk/document-ai";

const documentAi = new DocumentAi({
  serverURL: "https://api.abbyy.com/document-ai",
  apiKeyAuth: process.env["DOCUMENTAI_API_KEY_AUTH"] ?? "",
});

async function run() {
  const result = await documentAi.documents.list({
    cursor: "<optional_pagination_cursor_goes_here>",
  });

  for await (const page of result) {
    // Handle the page
    console.log(page);
  }
}

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 use the "beforeRequest" hook to to add a custom header and a timeout to requests and how to use the "requestError" hook to log errors:

import { DocumentAi } from "@abbyy-sdk/document-ai";
import { HTTPClient } from "@abbyy-sdk/document-ai/lib/http";

const httpClient = new HTTPClient({
  // fetcher takes a function that has the same signature as native `fetch`.
  fetcher: (request) => {
    return fetch(request);
  }
});

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 DocumentAi({ 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 { DocumentAi } from "@abbyy-sdk/document-ai";

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

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

Was this page helpful?