SDKs

Three official client libraries are published:

Language	Package	Version	Registry	Guide
TypeScript	@retorna-tech/retorna-gateway-sdk	1.0.4	npm	Guide
Python	retorna-gateway-sdk	1.0.4	PyPI	Guide
Java	app.retorna:retorna-gateway-sdk	1.0.3	Maven Central	Guide

What they all do for you

Every SDK wraps the same public API and takes the same four things off your plate:

• Token exchange — acquires and caches your OAuth2 token; there is no refresh token, so the SDK just asks again when it is close to expiring.
• Request signing — builds the RSA-SHA256 signature and nonce headers for you, from your provisioned private key.
• Retries — retries transient failures with backoff, configurable per client.
• Typed models — request and response shapes as native types in each language, so a contract change surfaces at compile time, not at runtime.

They also all send identity headers on every request, so a call is traceable to the exact SDK and version that made it.

Prefer raw HTTP?

Nothing here blocks an integration. The API is plain HTTP over JSON, and the two parts a library would normally hide for you are documented step by step, with runnable snippets in several languages:

• Authentication — the client_credentials token exchange.
• Request signing — the signature and nonce headers, with a worked example of the exact string that gets signed.

From there, every endpoint in the API Reference carries a request/response example and a "Try it" panel you can call directly from the browser.