Python helper
Uses the Python standard library. No PyPI package is required for the beta kit.
from teleza_client import TelezaClient
client = TelezaClient(
api_url=os.environ["TELEZA_API_URL"],
api_key=os.environ["TELEZA_API_KEY"],
)
report = client.create_report(
name="User Directory",
data_source_id="InMemory",
sql="Users",
output_format="json",
)
client.export_report(report["id"], "pdf", "user-directory.pdf")
TypeScript helper
Uses modern built-in fetch. No npm package is required for the beta kit.
import { TelezaClient } from './telezaClient';
const client = new TelezaClient(
process.env.TELEZA_API_URL!,
process.env.TELEZA_API_KEY!
);
const report = await client.createReport({
name: 'User Directory',
dataSourceId: 'InMemory',
sql: 'Users',
format: 'json'
});
const pdfBytes = await client.exportReport(report.id, 'pdf');
Supported beta formats
- excel
- xlsx
- csv
- json
- jsonl
- ndjson
Why copy-paste first?
This keeps the beta surface small and predictable. The .NET SDK is packaged; Python and TypeScript stay dependency-light until design partners prove that PyPI or npm distribution is worth the extra maintenance.
Future SDK readiness
Teleza also runs deterministic OpenAPI-generated SDK evidence for future TypeScript Fetch, Python, and Go clients. That proves the API contract can produce typed client surfaces as the platform grows, without creating public package-support obligations during private beta.
These generated clients are evidence artifacts only. They are not official npm, PyPI, or Go module releases until their authentication examples, binary response handling, error handling, package versioning, install tests, and publish rehearsal are reviewed and promoted.
Current supported paths: packaged .NET SDK, Python copy-paste kit, TypeScript copy-paste kit, and raw REST/OpenAPI.