TaxMaxi instance.
Authentication modes
The SDK supports three ways to authenticate, each suited to a different runtime:| Mode | Factory | When to use |
|---|---|---|
| API key / bearer token | new TaxMaxi({ apiKey }) | Server-side scripts, CLI tools, and automated pipelines where you hold a session token |
| Browser session (cookie) | TaxMaxi.fromBrowserSession() | Browser apps that authenticate via your own login flow and rely on session cookies |
| Server-side request forwarding | TaxMaxi.fromRequest({ cookieHeader }) | SSR frameworks (Next.js, SvelteKit, etc.) that need to forward incoming cookies |
Quick example
The following example installs the package, creates an API-key client, lists your sources, and computes a German tax summary for 2024.Two API surfaces
EveryTaxMaxi instance exposes the same operations through two namespaces:
- Promise-based (
client.sources,client.auth) — the default interface. Methods return standardPromisevalues. Use this for most applications. - Effect-based (
client.effect.sources,client.effect.auth) — an advanced interface that returns Effect values instead of Promises. Use this if you are already composing Effect pipelines.
The Effect interface is intended for advanced use cases. If you are new to TaxMaxi or to Effect, start with the Promise-based interface.
Next steps
Installation
Install the package and configure your client for API key, browser session, or SSR usage.
Sources
List sources, run sync jobs, and compute tax summaries using the SDK.
Error handling
Catch and inspect
TaxMaxiError values with typed status codes and field errors.API reference
Browse the full REST API that the SDK wraps.