Skip to content

Developers

Python SDK availability

Overview

The former Python SDK smoke example used an unavailable public package. A public hosted Python SDK and its methods are not established here; contact Zof for deployment-specific API support.

Contact Zof for access for your deployment, including API integration support.

Who should read this

  • Developers and platform teams planning how Zof will connect to their pipelines, test reports and internal tools.

When to use this workflow

  • Plan an integration with your CI pipeline, test runner or internal tooling.
  • Confirm which interfaces and credentials a deployment provides before building against them.

Step-by-step procedure

Describe the integration

List the pipelines, test reports and environments you want Zof to work with, and the languages your team uses.

Request access

Contact Zof with that outline. Access is arranged for your deployment rather than through a public package.

Keep credentials out of code

Store any credentials for your deployment in a secret manager or CI secret store, never in committed files.

Availability

Public SDKs
Hosted SDK packages and method references are not documented on this site.
Developer access
Arranged with Zof for each deployment, together with the interfaces and credentials it uses.
Integration support
Contact Zof for API integration support for your deployment.

Best practices

  • Agree the interfaces and versions your deployment uses before building against them.
  • Keep existing code review, tests and CI checks in place while you evaluate an integration.

Access request outline

Organization: <your company>
Deployment or evaluation: <name>
Language: Python
Smoke check scope: <service, pipeline or report>
Contact: <work email>

Was this page helpful?