Developers
SDKs
Official client libraries for Node.js, Python, Go, and Java.
Overview
Official SDKs provide typed interfaces, automatic retries, pagination helpers, and idempotency key support for Node.js, Python, Go, and Java codebases.
Prefer SDKs over raw HTTP when building internal platforms, custom dashboards, or long-running workers that integrate with Zof.
Who should read this
- QA engineers, SREs, platform teams, and developers operating Zof Console and APIs.
When to use this workflow
- Onboarding new team members to Zof terminology and workflows
- Authoring internal runbooks aligned with Console labels
- Designing CI/CD or webhook integrations against documented behavior
Step-by-step procedure
Confirm access
Verify organization membership and role permissions in Admin Center.
Confirm API key or SSO session is scoped to the correct tenant.
Apply this guidance
Follow Console navigation paths and API examples in this document.
Use staging project and environment IDs for first-time integration tests.
Verify outcomes
Check Operate → Runs, Quality areas, or API responses for expected results.
Update team runbooks when your stack requires environment-specific variations.
Key concepts
- Node.js / TypeScript
- npm install @zof-ai/sdk
- Python
- pip install zof-ai
- Go
- go get github.com/zof-ai/zof-go
- Java
- Maven: ai.zof:sdk
Best practices
- Validate changes in staging before applying release gates to production.
- Include run IDs and timestamps when escalating issues to support or auditors.
- Align internal runbook terminology with Zof Console UI labels for clarity.
Node.js
import { ZofClient } from '@zof-ai/sdk';
const client = new ZofClient({ apiKey: process.env.ZOF_API_KEY });
const run = await client.runs.create({
projectId: 'proj_abc123',
environment: 'staging',
testCaseIds: ['tc_001'],
});
await client.runs.waitUntilComplete(run.id);Was this page helpful?