Available SDKs

The SDKs are thin wrappers around the OpenAPI document — they handle authentication, retries, idempotency, pagination, and webhook signature verification, and they offer typed models so your editor fills in the rest.

First-party SDKs

Language	Package	Status
.NET / C#	`Paylera.Sdk`	GA
Node.js / TypeScript	`@paylera/sdk`	GA
Go	`github.com/paylera/paylera-go`	GA
Python	`paylera`	Beta
Ruby	`paylera`	Beta
Java	`io.paylera:paylera-sdk`	Beta

GA SDKs follow the same versioning policy as the API — a release line per dated API version with at least 12 months of support.

What every SDK does

Authentication — pass a key once at construction; every call carries it.
Retries — automatic retry on 429 and 5xx with jittered exponential backoff, capped at 5 attempts.
Idempotency — auto-generates idempotency keys for POSTs, with an option to override per call.
Pagination — list() returns an iterator; for-each walks pages for you.
Webhook verification — Webhooks.verify(payload, header, secret) does the right thing.
Money — provides a typed Money value type so you don’t trip over decimals.
Telemetry — sets a User-Agent so we can investigate issues per-SDK; does not collect any of your data.

What every SDK doesn’t do

Inject opinions about your DI container. SDK clients are plain classes you can wire how you want.
Persist tokens. You bring the secret manager.
Magic global state. Multiple instances run side-by-side without conflict.

Picking a version

@paylera/sdk@2026.4.x   targets API version 2026-04-01
@paylera/sdk@2025.10.x  targets API version 2025-10-01

Within a major (2026.4.*) we ship non-breaking improvements freely. Across majors, follow the migration notes in the Changelog.

When to skip the SDK

The OpenAPI document is publicly available. Generate your own client in any language with one of the well-known generators; the result will work. The first-party SDKs save you the boilerplate and keep up with API additions automatically — most teams use them.