Skip to main content
Bachs SDKs handle the parts of an integration every app needs: authenticating requests, typed responses, safe retries and webhook signature checks. You write the parts that are yours, such as orders, access and fulfilment. Every SDK calls the same Bachs API. Anything you can do with an SDK, you can also do with a plain HTTP request.

​
Server-side SDKs

Use a server-side SDK from your backend, where your secret API key lives. Never use one in a browser or a mobile app. The Node.js SDK guide covers installing it, creating a client, sending requests, handling errors and verifying webhooks. For another server language, call the API directly, or try a community SDK.

​
Browser SDK

The overlay checkout opens a Bachs checkout in a modal on your own page. Load it with a script tag or install it from npm. It never sees card details, and it needs no API key: your server creates the checkout session and the browser only opens it.

​
Developer tools

  • Bachs CLI: forward webhooks to localhost, trigger sample events, and call any API operation from your terminal.
  • Bachs skill: give your coding assistant the Bachs integration rules, including when to use the SDK.
  • Starter templates: Next.js apps with checkout, subscriptions and webhooks already wired up with the SDK.
  • API reference: every endpoint, parameter and response, including the operations the SDK does not cover yet.

​
Community SDKs

Developers have built SDKs for Python, Go, Rust and PHP. Bachs does not maintain or review them, so check what a library covers before you depend on it. Browse them in Community projects. The official Node.js package is @bachs/sdk. A community package called bachs-sdk is unrelated to it.

​
Versioning

Official SDKs use semantic versioning. The SDK version and the API version are separate: SDK 1.x calls API /v1. See SDK versioning and support.