Skip to main content
The library wraps the APIs so you can parse and extract documents from TypeScript and JavaScript. The library is published as the landingai-ade package and generated from the API specification. The Gen2 APIs live under the client.v2 sub-client. It exposes both processing modes: async jobs through client.v2.parseJobs and client.v2.extractJobs, and synchronous calls through client.v2.parse and client.v2.extract. Jobs accept larger documents, default to the lower-consumption standard service tier, and suit automated pipelines and background work. See Sync vs Async Processing.

Install the Library

Set Your API Key

The library reads your API key from the VISION_AGENT_API_KEY environment variable. Generate an API key first, then set it using any of the methods below. Do not hard-code your API key in source files.

Method 1: Set the API Key as an Environment Variable

  1. Set the environment variable. To persist the key across sessions on macOS or Linux, add the export command to your shell profile (.zshrc or .bashrc), then run source ~/.zshrc.
  2. Initialize the client. It reads the VISION_AGENT_API_KEY environment variable automatically:

Method 2: Store the API Key in a .env File

Store your API key in a .env file. The library reads the key from the environment; it does not load .env files on its own, so use the dotenv package to load the file.
  1. Install the dotenv package:
  2. Create a .env file in your project root and add your API key:
  3. Load the .env file before you initialize the client:
In Node.js 20.6 or later, you can skip the dotenv package and run your script with node --env-file=.env your-script.js.

API Key Precedence

If the API key is set in more than one place, the library resolves it in this order (the first match wins):
  1. The apikey passed to the client constructor.
  2. The VISION_AGENT_API_KEY environment variable, whether you set it directly or loaded it from a .env file. A value already set in your environment is not overridden by a .env file.
For help with missing-key errors, keys that fail to load, or keys that resolve to the wrong account, see Troubleshoot API Key Issues.

Initialize the Client

Create a client. It reads VISION_AGENT_API_KEY from the environment automatically.
By default, the library uses the US endpoints. If your API key is from the EU region, set the environment option to eu. API keys are region-specific: an EU key works only with the EU environment.
For more about using in the EU, see European Union (EU).

Parse a Document

Use client.v2.parseJobs to convert a document into Markdown, a structure tree, and per-element grounding. The sub-client exposes create, get, list, and wait. The wait method polls until the job reaches a terminal state and returns the finished job. Pass a local file as a read stream with the document parameter, or a remote file with document_url. Setting service_tier to standard runs the job in the lane that consumes half the credits of priority. A finished job carries the parse output in result, a V2ParseResponse with markdown, structure, and metadata. For the full workflow and parameters, see Parse Asynchronously.

Extract Data

Use client.v2.extractJobs to pull structured fields from parsed Markdown. Provide the Markdown as a string with markdown (or a remote URL with markdown_url) and a schema. The schema parameter accepts a JSON Schema object or a JSON string. A finished job carries the extraction in result, a V2ExtractResult with extraction, extraction_metadata, markdown, and metadata. For the full workflow and parameters, see Asynchronous Extraction.
To define a typed schema, use Zod (v4 or later) and pass z.toJSONSchema(YourSchema) as the schema.

Set the Model Version

The model parameter is optional. When you omit it, the API uses the latest model. To select a family or pin a version, pass a model string such as dpt-3-verity, or a dated snapshot. See Parsing Models. Responses parsed with dpt-3-verity include a confidence score on each word-level atomic_grounding entry. See Word Confidence Scores.

Save Output to a File

The job create methods do not accept saveTo. To keep a job’s output, write result to a file yourself, or pass output_save_url on create to have deliver the result straight to your own storage. See Save Parsed Output to a URL. The synchronous parse and extract methods take an optional saveTo parameter instead, which writes the full response to a JSON file. Pass it a directory to use an auto-generated file name, or a path ending in .json to choose the exact file.

Handle Errors

The synchronous parse and extract methods throw V2SyncTimeoutError if the request exceeds the server’s synchronous time limit (HTTP 504). For large documents, use the async jobs interface instead. When a parse partially succeeds (some pages fail), the API returns the full response with an HTTP 206 status, and the failed pages are listed in metadata. See Troubleshoot Parsing. The job wait method returns the finished job regardless of outcome, so check job.status. To throw instead when a job fails, pass raiseOnFailure: true, which throws JobFailedError. If a job does not finish within the timeout, wait throws JobWaitTimeoutError. These v2 helper errors do not extend APIError, so catch them by name.

Additional Resources