Skip to content
DISHA 4.0 HCOS
A software engineer studying code across two monitors in a modern office

RESOURCES → DEVELOPER CENTER → DOCUMENTATION

Build With DISHA. Understand the System Before You Integrate It.

From architecture and concepts to APIs, events, security and production operations — everything developers need in one technical system. This is the canonical learning layer, not an API catalogue.

How can a developer understand DISHA deeply enough to build correctly — not merely find an endpoint?

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.
Browse Documentation
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?

Documentation Path Builder

Pick your seat at the table — get the reading order that matters for it.

Reading path — Backend · 5 stops · ~40 min

  1. 01Architecture & tenancyPlatform Foundations10 min
  2. 02Authentication & scopesGetting Started7 min
  3. 03Data ingestion & synchronizationDeveloper Guides9 min
  4. 04Idempotency, retries, paginationOperations8 min
  5. 05Webhook verificationDeveloper GuidesOpen →

Architecture Explorer

Click a layer of Experience → Gateway → Services → Intelligence → Data/Knowledge → AI Orchestration → Events → Observability to see purpose, inputs, outputs, dependencies and governance constraints.

Purpose

Capability mapping, readiness, matching, scoring

Inputs

Governed data, evidence

Outputs

Explainable outputs with provenance

Dependencies

Data/Knowledge · AI Orchestration

Governance constraints

Observed/inferred kept distinct

The documentation library

Getting Started

  • Prerequisites, access & environments
  • Authentication & identity mapping
  • Your first integration, request, event & workflow

Platform Foundations

  • Architecture & tenancyPlatform OverviewOpen →
  • The Human Capital GenomeHuman Capital GenomeOpen →
  • The Human Digital TwinHuman Digital TwinOpen →
  • Career Intelligence GraphCareer Intelligence GraphOpen →
  • Readiness IntelligenceReadiness IntelligenceOpen →
  • AI orchestration & agents

Developer Guides

  • Identity mapping
  • Data ingestion & synchronization
  • Event-driven workflowsOpen →
  • AI-agent integration
  • Analytics & testing

Product & Domain Docs

  • Talent Acquisition · Learning · Performance · Career
  • MarketplaceOpen →
  • Industry solutionsOpen →

Data & Intelligence

  • Schemas, evidence & provenance
  • Confidence, scoring & graph relationships
  • Temporal data & lineage

Security & Governance

  • Access control, isolation & encryption
  • Privacy, retention & audit
  • Human oversight requirements

Operations

  • Deployment & monitoring
  • Rate limits, retries & idempotency
  • Incident handling & change managementOpen →

Every article follows one anatomy

1. Purpose2. When to use3. Prerequisites4. Concepts5. Architecture6. Configuration7. Example8. Failure modes9. Security/Governance10. Observability11. Related APIs/SDKs/Webhooks12. Version/compatibility13. Next steps

Developer onboarding flow

1. Access2. Sandbox/production context3. Identity & authentication4. Architecture primer5. First request6. First webhook7. End-to-end workflow8. Retries/idempotency/observability9. Acceptance checklist10. Production readiness

Troubleshooting Lens

Symptom

401 on every call after rotating keys

Likely causes

Stale token cache; clock skew; wrong environment

Diagnostics

Decode token; check env base URL; verify secret version

Remediation

Refresh token; sync clock; pin environment

Escalation

Auth runbook → support with correlation ID

Sample article — code that states its assumptions

TypeScript · example · v1.2 · not production-ready · illustrative
const res = await disha.readiness.get("person_123", {
  // population & period travel WITH the number — never a bare score
  disclosure: true,
});
// res.state · res.population · res.period · res.data_status
// Illustrative SDK design — no official package is published yet.
Was this page accurate?

Docs governance: every domain has an owner, review workflow, version/date and deprecation policy; AI-drafted docs require human review; examples are validated against contracts or marked illustrative. The Developer Center is ready only when a developer can move from a conceptual question to a working integration — and from a production problem back to the exact contract, event, release or incident that explains it — without contradictory definitions or undocumented behavior.