Sanvro logoSanvro.
ABDM BRIDGE · FOR HIMS, EHR & HOSPITAL APPS

Days of ABDM work.
Done in hours.

Your HIMS, EHR or hospital app sends Sanvro one simple request. We do the heavy lifting across the ABDM network and send a webhook when it's done. 90% less build cost.

Get sandbox accessBuild it with your coding agent
DIRECT ABDM BUILD
Gateway sessions & auth
ABHA creation flows
Care-context linking
Fidelius encryption
Consent & data transfer
Callbacks & bridge URL
Certificates & signing
Sandbox & certification tests
EFFORTDays
BUILD COST−90%
100%
REQUESTS YOU SEND0
ABDM EXCHANGES WE HANDLE0
WEBHOOKS BACK TO YOU0
LINES OF ABDM CODE YOU WRITE0
NEWSanvro MCP for your coding agent

You send one request.
We carry ABDM.

Your HIMS, EHR or hospital app sends Sanvro a simple request. We do the heavy lifting on the ABDM network and ping your webhook when it's done.

Get sandbox accessWatch a request cross
90%less build effort and cost
Hoursnot months, with MCP
1 + 1API and webhook
0ABDM crypto in your code
your-editor · agent · opd-modulesanvro-mcp
youAdd ABDM visit linking to our OPD module▍
DIRECT ABDM BUILDDays
WITH SANVRO MCPHours

Six lines in. Everything ABDM needs, out.

SANVRO // ABDM_BRIDGErequest #1042 · care-context link
PHASE · REQUEST INLIVE
L0 · YOUR APPHIMS · EHR · HOSPITAL
What you write
POST /v1/linking/care-contexts
{
  "abhaAddress": "asha@abdm",
  "facility": "city-clinic",
  "careContext": "visit-0412"
}
WEBHOOK INBOX
waiting for event…200 ✓
SANVRO BRIDGE0/6 DONE
The heavy lifting
L01
Gateway sessiontokens · refresh
queued
L02
Network headersrequest id · timestamp · HIP id
queued
L03
Fidelius encryptionECDH · key exchange
queued
L04
Bridge & certificatesbridge URL · signing
queued
L05
Callbacks & consentasync · waits for people
queued
L06
Audit & webhookids · signed event
queued
ABDM NETWORK0 CALLS
What we talk to
GATEWAY
ABHA
HIP
HIU
PHR APP
CONSENT
EVENT STREAM
10:40:02.114APPPOST /v1/linking/care-contexts202
Hover a Sanvro layer to inspect what it does for you.bridge.live · 1 request in · 1 webhook out · illustrative
THE SPLIT

You keep the product. We keep the plumbing.

Business fields go in. Ids and a status come back. Nothing on the right ever lands in your codebase.

mobile · OTP · ABHA addressfacility · care contextdates · record type
01SANVRO
Gateway sessionsTokens opened, refreshed and kept alive.
02SANVRO
ABDM headersRequest id, timestamp and HIP/HIU headers on every call.
03SANVRO
Fidelius encryptionECDH key exchange and record encryption.
04SANVRO
Bridge URLRegistered with ABDM and served by Sanvro.
05SANVRO
CertificatesHeld, rotated and used for signing.
06SANVRO
Async callbacksCaught from the network and matched to your request.
07SANVRO
Waiting for peopleOTP and consent steps pause until the patient acts.
08SANVRO
Audit + signed webhookIds and status delivered to your endpoint.
SANVRO MCP

Plug into your coding tool. Days of ABDM work, done in hours.

Add the Sanvro MCP server to Cursor, Claude Code, VS Code or any MCP-ready agent. It loads journey skills for ABHA, linking, sharing and consent, so your agent writes the integration against our API.

  1. 01 · CONNECTAdd one server
    {
  "mcpServers": {
    "sanvro": {
      "url": "{SANVRO_MCP_URL}"
    }
  }
}
  2. 02 · ASKDescribe the journey
    "Create ABHA at registration""Link every OPD visit""Request consent, then fetch"
  3. 03 · SHIPTest on sandbox, go live

    The agent pauses where a person must act: the patient reads their OTP and approves consent in their own app. It never invents either.

    care_context.linked · 200
FOUR JOURNEYS · ONE API
01
Create an ABHANumber or address, or scan and share at the counter.
abha.created
02
Link a visitAttach the visit's care context to the ABHA.
care_context.linked
03
Share a recordSend to the organisation allowed to receive it.
record.shared
04
Consent, then fetchPatient approves in their app. Record arrives on your webhook.
consent.granted
Sandbox to production
SANVRO_BASE_URL=https://sandbox.api.sanvro.com

await sanvro.linking.link({
  abhaAddress, facility, careContext
})

One variable changes. Every call stays the same.

Go live on ABDM without building ABDM.

Get a sandbox key and the MCP server. Your team can wire the first journey today.

or write to sales@livconnect.ai
Contact Us