SDKs

Kessel provides official SDKs for multiple languages. Each SDK handles connection management, authentication, and serialization so you can focus on integrating with Kessel’s APIs.

All SDKs use gRPC, which is Kessel’s primary protocol.

Available SDKs

Language	Repository	Install from
Go	kessel-sdk-go	go get
Python	kessel-sdk-py	PyPI
Java	kessel-sdk-java	Maven Central
Node.js	kessel-sdk-node	npm
Ruby	kessel-sdk-ruby	RubyGems

All SDKs follow a consistent package structure across languages. If you know one SDK, the others will feel familiar.

Browser SDK

A separate kessel-sdk-browser exists for browser environments. It uses HTTP (not gRPC) and implements a subset of the API, primarily CheckSelf endpoints. It does not follow the standard SDK specification above. If you have a use case that requires browser-based access, reach out to the team for guidance.

Getting started

For installation instructions and usage examples, see the getting started guide.

Getting started

For CI/CD setup including native compilation and Docker builds, see the SDK CI guide.

Setting up SDKs for CI

SDK package structure

Each SDK organizes its code into consistent packages:

• {service}.{version} contains generated client code for a specific API (e.g. inventory.v1beta2). This is where you find ClientBuilder for creating service clients.
• grpc contains gRPC-specific utilities like channel creation and authentication middleware.
• middleware contains transport-agnostic utilities such as token caching.
• rbac.v2 contains helpers for constructing common RBAC resource types.
• console contains helpers for ConsoleDot integration.

For SDK contributors

The full package specifications, including method signatures, interface contracts, and implementation rules, are maintained in the Client SDK Specification. If you are building or contributing to a Kessel SDK, start there.

API reference

For the underlying API definitions that the SDKs wrap, browse the protobuf definitions on the Buf Schema Registry.