Skip to main content

Overview

Atlas does not need a separate hand-written SDK to be useful from TypeScript. The source of truth is the OpenAPI contract, which also powers the generated Scalar reference. Use this page when you want typed functions in a TypeScript project and you are comfortable generating a client from the Atlas repo.
The generated client is built with Orval from openapi/atlas.openapi.json. It is repo-local output, not a separately versioned npm package.

When to generate a client

Generate a TypeScript client when:
  • You are building inside the Atlas app.
  • You want compile-time help for request and response shapes.
  • You need to keep a branch aligned with the current OpenAPI contract.
For one-off scripts, direct fetch calls may be clearer. For exact function names and types, inspect the generated file after generation.

Generate the client

The generated output lives at:

Use it safely

Import only the functions your workflow needs, and keep source evidence attached to any records you export.
If you need an API key, pass headers through the generated function options:
Do not ship API keys in browser bundles.

Keep generated code in sync

When backend API behavior changes, regenerate from the backend, then regenerate the app client:
OpenAPI JSON files are generated artifacts. Do not hand-edit them to make a TypeScript compile error disappear.

API reference

Inspect exact endpoint and schema names.

Authentication

Decide how the generated client should authenticate.

API quickstart

Try the underlying requests before wrapping them in a generated client.

Find source-backed actors

Keep source evidence attached when using generated functions.