SDK Generation

SDK codegen that runs on every spec merge.

TypeScript, Python, and Go SDKs generated and published automatically on every spec change. Semver bumped from spec diffs — breaking changes trigger a major, non-breaking changes bump patch or minor. No manual triggers, no stale packages, no consumers pinning to six-month-old releases because the SDK was never updated.

Get started free SDK Guides

TypeScript SDK (generated)

              import { ApistaqClient } from '@your-co/payments-sdk'
              const client = new ApistaqClient('YOUR_API_KEY')
              const payment = await client.payments.create({
                amount: 1999, currency: 'usd'
              })
            

TypeScript Published 2.1.0

Python Published 2.1.0

Go Published v2.1.0

The pipeline

Every spec change produces a publishable, versioned package.

Triggered on spec merge

Apistaq watches your OpenAPI source (GitHub, GitLab, or direct upload). On every spec change, generation runs automatically — no webhook to configure, no CI job to write.

Automatic semver versioning

Apistaq reads your spec version and derives the SDK version. Breaking changes auto-bump the major. Non-breaking changes bump patch or minor. Version pinning and manual override supported.

Publish to npm, PyPI, and pkg.go.dev

Connect your registry tokens in the dashboard. Apistaq handles the publish step with retry logic, attestation, and a release changelog entry generated from spec diffs.

Auto-generated changelog

Each SDK release gets a changelog entry derived from the spec diff — added endpoints, changed parameters, deprecated paths. Your consumers always know what changed.

Your consumers deserve an SDK that reflects your actual API.

SDK codegen is available on Builder and Platform plans. Start on the free plan to connect your spec and see the portal and versioning system before upgrading.

Start free