One client, both products
Xberg Enterprise and Xberg Pro serve an overlapping API. A single client covers both: pass a
target, or let the client read the tier from /healthz and gate the tier-specific methods
for you.
Xberg SDKs
One client per language, two products. Point it at an Xberg Enterprise or an Xberg Pro deployment and it exposes the shared surface plus the operations that tier actually serves.
Why these clients
Section titled “Why these clients”Extraction is asynchronous
Submitting returns job ids, not a document. The clients poll for you with a bounded wait and optional backoff, so a large file never rides on one long-lived HTTP request.
Generated from the served spec
Models come from the same OpenAPI documents the services emit, vendored into this repo and checked for drift, so the types describe what the server actually sends.
The same surface in three languages
Python, TypeScript and Go expose the same operations under each language’s own naming conventions, so a behaviour documented once holds everywhere.
Install
Section titled “Install”Python
pip install xberg-io-sdkTypeScript
pnpm add @xberg-io/sdkGo
go get github.com/xberg-io/sdks/packages/go