Skip to content
DISHA 4.0 HCOS
A focused programmer at dual monitors with headphones

RESOURCES → DEVELOPER CENTER → SDKS

Build DISHA Into the Stack You Already Know.

Client libraries that reduce boilerplate while preserving API transparency — typed contracts, auth, retries, pagination, events and observability, with every SDK method linked to the exact operation it wraps.

How can developers integrate DISHA using the language and engineering conventions they already use?

Developer honesty: no public API, SDK packages, webhook deliveries, release history or status monitoring are live yet. Every contract, payload and console below is a clearly-labeled illustrative design — no fabricated endpoints, SDK support, incidents or uptime figures.
SDKs
One Developer Center · six connected surfacesDocumentation How do I understand/build this?API Reference What exactly is the contract?SDKs How do I build this in my stack?Webhooks How do I respond to events?Release Notes What changed and what must I do?System Status Is anything operationally wrong?

Supported languages

Cards list only languages with an officially supported package — which today means none are published yet. The two below are the designed first targets of the SDK program, shown with the illustrative design; nothing here implies an installable package.

TypeScript

Designed target · not published

package design v1.2 · API v1.2 · webhook schema 1.1

Install (design) · illustrative · illustrative
// npm install @disha/sdk  — NOT YET PUBLISHED

Python

Designed target · not published

package design v1.2 · API v1.2 · webhook schema 1.1

Install (design) · illustrative · illustrative
# pip install disha-sdk  — NOT YET PUBLISHED

The SDK Wizard

Language

Runtime / framework

Use

Tailored starter — TypeScript · Node.js 20+ · Backend service

  1. 1. Reserve the package name in your private registry (@disha/sdk).
  2. 2. Configure environment: sandbox first, production behind approval.
  3. 3. Inject the token from your secret manager — never in code.
  4. 4. Start with read operations; wire idempotency keys before writes.
  5. 5. Subscribe to the events your backend service reacts to — see Webhooks.

Unsupported framework choices route to the raw API docs — no implied compatibility.

SDK Playground

TypeScript · GET /v1/genome/evidence/{person_id} · illustrative
import { DishaClient } from "@disha/sdk"; // ILLUSTRATIVE — not published

const disha = new DishaClient({
  token: process.env.DISHA_TOKEN!,        // never hardcode secrets
  environment: "sandbox",
  retries: { max: 3, backoff: "exponential" },
});

const res = await disha.genome.evidence.list("person_123");
console.log(res.provenance, res.data_status);

What every SDK ships

  • · Typed request/response models
  • · Authentication helpers
  • · Pagination iterators
  • · Documented retries/backoff
  • · Idempotency helpers
  • · Webhook signature verification
  • · Typed error classes
  • · Request IDs
  • · Logging hooks
  • · Async support where officially released

Lifecycle & governance

Install/pinning guidance, compatibility matrices, migration notes, deprecations and security advisories live in Release Notes and are linked from every SDK version. Secrets never appear in client-side examples; provenance, runtime support and a security-reporting route are published with each package.

SDK governance: install commands tested, examples compile in CI, API mappings complete, webhook verification documented, compatibility explicit, advisories visible. Today: an honest design studio — zero published packages implied.

Was this page accurate?