Downloads

The SDKs, the example integration and the Postman collections are currently distributed as direct downloads from this site. Publication to the public registries (npm, PyPI, Maven Central, the Go module proxy) is coming; the install steps below will keep working after that switch. Every artifact embeds its LICENSE (Apache-2.0) and NOTICE — the SDK code is Apache-licensed, while access to the Partner API itself is governed by the BudgetBakers Partner Terms of Service.

Server SDKs

TypeScript / Node.js - budgetbakers-partner-sdk-0.2.1.tgz

npm install ./budgetbakers-partner-sdk-0.2.1.tgz

Node ≥ 20, zero runtime dependencies, ESM + CJS, TypeScript types included.

Python - budgetbakers_partner_sdk-0.2.1-py3-none-any.whl (also as an sdist)

pip install ./budgetbakers_partner_sdk-0.2.1-py3-none-any.whl

Python ≥ 3.10, one dependency (httpx), fully typed.

Kotlin / JVM - partner-sdk-kotlin-0.2.1.zip (source, for Kotlin and Java)

unzip partner-sdk-kotlin-0.2.1.zip   # next to your project

// settings.gradle.kts
includeBuild("../partner-sdk-kotlin")

// build.gradle.kts
dependencies {
    implementation("com.budgetbakers:partner-sdk:0.2.1")
}

Java ≥ 17, Jackson and the Kotlin standard library as dependencies, blocking API callable from Java. The Maven Central path (com.budgetbakers:partner-sdk, no includeBuild) follows with the first registry release.

Go - partner-sdk-go-0.2.1.zip

Unpack it next to your module's directory (it unpacks into partner-sdk-go/), then point the module path at it from inside your module:

go mod edit -replace github.com/budgetbakers/partner-sdk-go=../partner-sdk-go
go mod tidy

Go 1.24 or newer, standard library only. After the first release the module installs from the Go module proxy with go get github.com/budgetbakers/partner-sdk-go and the replace line goes away.

Example integration

bb-partner-examples.zip - the demo-partner reference integration (a partner backend + wallet SPA against the sandbox).

Building a mobile app? It needs no SDK: see Mobile apps.

Postman

Two collections generated from the same OpenAPI specs as the API reference, plus an environment template:

• bb-partner-api-v2.postman_collection.json - the whole Partner API v2, one folder per tag.
• bb-partner-api-v1.1-lifecycle.postman_collection.json - the connection lifecycle actions still served under /v1: createConnection, deleteConnection, refreshConnection, reconnectConnection and revokeConnection.
• bb-partner-api.postman_environment.json - the variables both collections use: PARTNER_API_URL and BB_API_KEY.

Import all three into Postman, select the environment, and replace the BB_API_KEY placeholder with your sandbox key. The Docs page of the partner portal offers the same environment with your sandbox key already filled in. Every request sends the key as the X-Api-Key header; client-scoped requests also need the X-Client-Id header set to a client id.

Checksums

SHA256SUMS covers every file above:

shasum -a 256 --check --ignore-missing SHA256SUMS