SDKs
Official clients for the Rox Register API. Both implement the full integration surface, request signing, local hashing, retries, selective disclosure and webhook verification, so a correct integration is a few lines of your code, not a protocol implementation. Both are exercised against the same published JWS test vectors as the API itself.
Node.js
TypeScript-first client for Node 20+, ESM and CommonJS, zero runtime dependencies. Typed record views, webhook event parsing and selective disclosure helpers included.
npm install @rox-register/sdk
Python
Synchronous client for Python 3.10+, built on httpx and cryptography only. Context manager lifecycle, typed exceptions, webhook verification and field hashing helpers.
pip install rox-register
What both SDKs guarantee
•Request signing built in: every mutation carries the RRv1 detached JWS, re-signed with a fresh timestamp and nonce on every retry attempt.
•Local hashing: pass raw bytes and the SDK computes the SHA-256 digest in your process; document content never reaches Rox.
•Retries that respect the contract: 429 always retried honoring Retry-After; 5xx and network errors retried only when the call is safe to repeat (reads, and seals carrying an idempotency key).
•Defaults sized for slow networks: 60 second per-attempt timeout, 3 retries with jittered backoff.
•Typed errors mapped from the RFC 7807 problem document and its stable RR-code.
•Uniform sealing: a seal is validated or rejected immediately, then exactly one terminal outcome (anchored or failed) arrives asynchronously. The SDKs expose no anchoring options because there are none.
Prefer another language? Everything the SDKs do is specified in the API reference and the JWS vectors; the quickstart curl snippets show the raw protocol end to end.