Server SDKs: Node, Go, Python and more
Your backend talks to Toden with a secret key: to create sessions, read verification results, and make every Risk Intelligence call. This page says honestly what exists for each language today.
What is available
Do not add @myazahq/trust-sdk or any Toden server package as a dependency until this page lists it as published. An unpublished package name can be claimed by someone else on a public registry.
Client SDKs for capturing a verification (React, React Native, Flutter) are published. See Choose an SDK.
Call the API directly
The API is plain JSON over HTTPS, so every language works today. The examples below make the same Sandbox request: a transaction decision.
Set your key in the environment first. Never write it into source.
What you should see: a 2xx response whose assessment.summary.outcome is allow, review or block. Sending the same request again with the same Idempotency-Key returns the original decision. The full walkthrough is the Risk Intelligence quickstart.
Rules every server integration must follow
- The secret key comes from the environment or a secrets manager. It never reaches a browser, a mobile app, a log line or a repository.
/api/kycand/api/v1return different error bodies. Parse each one separately. See Errors.- Make writes safe to retry. See Requests, retries and idempotency.
- A failed or timed-out risk decision is not an approval.
- Verify every webhook signature on the raw request bytes. See Verify signatures.
Generate a client from the contracts
Both API contracts are OpenAPI 3.1 documents, so you can generate a typed client in your own language today.
Go
Any language
These are third-party generators and the output is yours to maintain. They are labelled here as a working route, not as supported Toden SDKs. A client you generate is only as current as the contract you generated it from, so regenerate when the changelog announces a change.