Skip to main content
Every SDK follows the same OpenAPI definition, authentication rules, idempotency requirements, error envelope and request identifiers.
JavaScript, Python, Go, .NET and Rust public betas are available from their standard package registries. The source repositories remain available for review and reproducible builds.

Choose a client

Each client is available from its public repository for Sandbox integration. The repository owns its source-install path, compatibility policy, release checks and provenance.

Build from source

Install public beta

The published packages are available on npm, PyPI, pkg.go.dev, NuGet and crates.io.

Make the first request

Sandbox keys return fictitious records. Keep secret keys in server-side secret stores and retain the request identifier when tracing a failed call.

Write safely

All clients preserve the REST API’s write controls:
  • caller-owned idempotency keys for replay-safe writes;
  • bounded retries only where the operation and key make retry safe;
  • typed errors with HTTP status, stable error code and request identifier;
  • integer minor units for money;
  • no automatic exposure of raw response bodies in errors.
The REST reference remains authoritative for resource behavior, scopes and error codes.

Command line

hey checks local configuration and makes authenticated read requests against Sandbox projects.

Verify API compatibility

API definition

Inspect the versioned OpenAPI schemas, scopes, errors and Assurance Graph.

Proving Ground

Run API, financial-identity, bitemporal and adversarial conformance suites.
Last modified on September 3, 2026