# Eka Developer Platform APIs
## Docs
- [Get Started](https://developer.eka.care/user-guides/get-started.md): SIGN UP. BUILD. DEPLOY. 🚀
- [Eka Products](https://developer.eka.care/user-guides/eka-products.md): Explore all Eka platform products across Core EMR, Health AI, Interoperability, and MCP.
- [Open Source](https://developer.eka.care/user-guides/open-source.md): Eka's open source projects, SDKs, models, datasets, and publications.
- [EkaAgents Changelog](https://developer.eka.care/integrations/changelog/eka-agents.md): Feature releases, improvements, and fixes across the chatbot widget, MedAssist SDK, MCP server, and AI layer.
- [EkaScribe Changelog](https://developer.eka.care/integrations/changelog/ekascribe.md): Feature releases, improvements, and fixes across EkaScribe — extension, web, mobile, and AI.
- [Release notes — April 8, 2026](https://developer.eka.care/integrations/changelog/release-notes-2026-04-06.md): Daily release notes covering all changes shipped the week of March 31 – April 8, 2026.
- [Weekly update — Week of March 31, 2026](https://developer.eka.care/integrations/changelog/weekly-update-2026-04-06.md): Weekly summary of user-facing changes shipped March 31 – April 8, 2026.
- [Under the hood — March 2026](https://developer.eka.care/integrations/changelog/under-the-hood-march-2026.md): Monthly transparency post covering infrastructure, reliability, performance, and security work across the Eka platform in March 2026.
- [Assessments](https://developer.eka.care/integrations/health-ai/assessments.md): Structured capture of patient-reported health data across care journeys
- [EkaScribe](https://developer.eka.care/integrations/health-ai/ekascribe.md): Clinical and enterprise use cases for medical-grade speech-to-documentation APIs
- [MedAssist](https://developer.eka.care/integrations/health-ai/medassist.md): Agentic medical assistant for real-time medical conversations using medical LLMs
- [Medical DB](https://developer.eka.care/integrations/health-ai/medical-db.md): Standardized medical reference database for structured clinical knowledge
- [Medical Document Parsing](https://developer.eka.care/integrations/health-ai/medical-document-parsing.md): Extract structured clinical data from lab report documents
- [Medical Entity Codification](https://developer.eka.care/integrations/health-ai/medical-entity-codification.md): Map free-text medical entities to standardised ontology codes for structured, interoperable health data
- [MCP for Indian treatment protocol searchs](https://developer.eka.care/integrations/mcp/MCP-for-Indian-treatment-protocol-search.md): India-specific drug, protocol, and pharmacology intelligence APIs
- [MCP for EMR](https://developer.eka.care/integrations/mcp/mcp-for-emr.md): Self-hosted MCP server bridging Eka.care APIs with LLM applications
- [ABDM](https://developer.eka.care/integrations/interoperability/abdm.md): Plug-and-play APIs to integrate healthcare systems with India's ABDM ecosystem
- [Patient](https://developer.eka.care/integrations/core-emr/patients.md): Patient profiles and demographic records within Core EMR
- [Doctor](https://developer.eka.care/integrations/core-emr/doctor.md): Medical professional profiles and availability within Core EMR
- [Appointment](https://developer.eka.care/integrations/core-emr/appointments.md): Scheduled patient–doctor interactions within Core EMR
- [Clinic](https://developer.eka.care/integrations/core-emr/clinic.md): Healthcare facility profiles within Core EMR
- [Payments](https://developer.eka.care/integrations/core-emr/payments.md): Financial transactions for patient services within Core EMR
- [Prescription](https://developer.eka.care/integrations/core-emr/prescription.md): Medical prescriptions and treatment instructions within Core EMR
- [Overview](https://developer.eka.care/integrations/console/overview.md): Manage your agents, datasets, and integrations from the EkaCare Developer Console
- [Dataset](https://developer.eka.care/integrations/console/dataset.md): Attach your own doctors, facilities, and services so EkaCare agents can search and operate on your data
- [Doctor Dataset](https://developer.eka.care/integrations/console/doctor-dataset.md): Attach your list of doctors so agents can find and recommend them based on specialty, name, city, or facility
- [Facility Dataset](https://developer.eka.care/integrations/console/facility-dataset.md): Attach your hospitals, clinics, and care centres so agents can help users find the right place to visit
- [Service Dataset](https://developer.eka.care/integrations/console/service-dataset.md): Attach your medical services, tests, and procedures so agents can answer questions about what you offer
- [Getting started](https://developer.eka.care/api-reference/authorization/getting-started.md)
- [Connect Login](https://developer.eka.care/api-reference/authorization/client-login.md): Authorization APIs to get access and refresh token
- [Connect Refresh](https://developer.eka.care/api-reference/authorization/refresh-token-v2.md): Get new Authorization token using the refresh token
- [Delete Account](https://developer.eka.care/api-reference/authorization/delete-account.md): Delete User Privacy Data
- [Oidc Verify](https://developer.eka.care/api-reference/authorization/oidc-user-verify.md): Connect Client Auth Verify and Eka Token
- [Oidc Refresh](https://developer.eka.care/api-reference/authorization/oidc-user-refresh.md): Connect Client Auth Refresh
- [Python SDK](https://developer.eka.care/api-reference/authorization/sdks/python-sdk.md): A Python SDK for interacting with Eka Care APIs.
- [Go SDK](https://developer.eka.care/api-reference/authorization/sdks/go-sdk.md): A GO SDK for interacting with Eka Care APIs.
- [Java SDK](https://developer.eka.care/api-reference/authorization/sdks/java-sdk.md): A Java Spring Boot SDK for interacting with Eka Care APIs.
- [Invite flow](https://developer.eka.care/api-reference/authorization/invite-flow.md)
- [Bring Your Own Auth (BYOA)](https://developer.eka.care/api-reference/authorization/byoa.md): Authenticate your own users to EkaCare agents with an encrypted JWE token signed by your shared secret
- [Encrypted API Requests and Responses](https://developer.eka.care/api-reference/end-to-end-encryption/guide.md): Guide for implementing end-to-end encryption using JWE for Eka Care APIs
- [Getting Started](https://developer.eka.care/api-reference/connect/webhooks/getting-started.md)
- [Webhook Signature](https://developer.eka.care/api-reference/connect/webhooks/webhook-signature.md)
- [Register Webhook](https://developer.eka.care/api-reference/connect/webhooks/register-webhook.md): Registers a new webhook triggered by specific events. Each webhook is linked to a `business_id`, `client_id`, `endpoint`, and `event_names` defining the events that trigger it. The service sends POST requests to the specified URL for these events. The URL must be reachable and preferably secure (HTT…
- [Get Webhooks](https://developer.eka.care/api-reference/connect/webhooks/get-webhooks.md): Retrieves all registered webhooks. This endpoint allows partners to get a list of all webhooks that have been registered. Each webhook in the list includes details such as the unique identifier, event names that trigger the webhook, the endpoint URL, the signing key (if provided), the client ID, the…
- [Delete a Webhook](https://developer.eka.care/api-reference/connect/webhooks/delete-webhook.md): Deletes an existing webhook based on its ID. This endpoint allows partners to remove a previously registered webhook by specifying its unique identifier in the path parameter. The `id` parameter is required and must match the ID of the webhook to be deleted. Upon successful deletion, the service wil…
- [Webhook Samples](https://developer.eka.care/api-reference/connect/webhooks/webhook-samples.md)
- [Overview](https://developer.eka.care/api-reference/health-ai/assessment/overview.md)
- [Overview](https://developer.eka.care/api-reference/health-ai/assessment/assessment-flow/overview.md)
- [Step 1. Initialization](https://developer.eka.care/api-reference/health-ai/assessment/assessment-flow/initialization/initialize-assessment.md): This API is used to initialize the assessment. It returns an assessment_id that uniquely identifies the assessment session. This API must be called to initiate a user assessment
- [Step 2. Start Assessment](https://developer.eka.care/api-reference/health-ai/assessment/assessment-flow/continue/start-assessment.md): This API is used to start and get the first question of the assessment. Use this API to get the first question.
- [Step 3. Continue Assessment](https://developer.eka.care/api-reference/health-ai/assessment/assessment-flow/continue/continue-assessment.md): This API is used to submit user answers and get the next questions based on the answers. Call this API multiple times until the assessment is complete where `is_last_question` will be true
- [Step 4. Submit Assessment](https://developer.eka.care/api-reference/health-ai/assessment/assessment-flow/submit/submit-assessment.md): This API is used to Submit the assessment. This api should be called after the assessment is completed and progress reaches 100%. Use this API to submit the assessment and get assessment summary
- [Get Assessment Data](https://developer.eka.care/api-reference/health-ai/assessment/questionnaire_data.md): This API retrieves the assessment data for a given assessment ID. The assessment data includes all the available information about `practitioner`, `patient` and `questionnaire`.
- [Get Questionnaire Data (V2)](https://developer.eka.care/api-reference/health-ai/assessment/questionnaire-v2.md): Fetch the full questionnaire (questions, answers, practitioner, patient, and scoring) for one or more assessment sessions. Unlike the v1 `questionnaire_data` endpoint, this API accepts multiple assessment IDs in a single request and requires authentication — only the owning business can retrieve its…
- [List all the components](https://developer.eka.care/api-reference/health-ai/assessment/component-info/list-all-components.md): This API is used to list all the components and the details about request and response format of each component. It includes the json schema of the request and response format of each component.
- [Fetch Grouped Assessments](https://developer.eka.care/api-reference/health-ai/assessment/fetch-assessment-v2.md): Fetch assessments from both Self-Assessment and Smartcheck modules.
- [Fetch assessments (Deprecated)](https://developer.eka.care/api-reference/health-ai/assessment/fetch-assessments-by-id.md): Fetch assessments for patients or doctors based on filters like status, workflow ID and date range.
- [Python SDK](https://developer.eka.care/api-reference/health-ai/assessment/SDKs/ekapython-sdk.md): Eka Python SDK for assessment
- [TS SDK](https://developer.eka.care/api-reference/health-ai/assessment/SDKs/assessment-ts-sdk.md): Complete implementation guide for the Assessment TS SDK
- [Assessment Workflows](https://developer.eka.care/api-reference/health-ai/assessment/assessment-workflows.md)
- [Symptoms dump](https://developer.eka.care/api-reference/health-ai/assessment/symptoms-dump.md)
- [Error Codes](https://developer.eka.care/api-reference/health-ai/assessment/error-codes.md)
- [↗️ Continue Assessment Request Format](https://developer.eka.care/api-reference/health-ai/assessment/assessment-flow/continue/continue-request-formats.md)
- [↙️ Continue Assessment Response Format](https://developer.eka.care/api-reference/health-ai/assessment/assessment-flow/continue/continue-response-formats.md)
- [EkaScribe](https://developer.eka.care/api-reference/health-ai/ekascribe-link.md)
- [MedAssist Agent](https://developer.eka.care/api-reference/health-ai/medassist/overview.md): MedAssist is a medical assistant agentic functionality that helps users communicate with our state of the art medical LLM for medical concerns and healthcare guidance.
- [Create Session](https://developer.eka.care/api-reference/health-ai/medassist/create-session.md): Creates a new MedAssist session that provides a session ID and session token for WebSocket communication.
- [Get Session](https://developer.eka.care/api-reference/health-ai/medassist/get-session.md): Retrieves the current status and details of an existing MedAssist session.
- [Refresh Session Token](https://developer.eka.care/api-reference/health-ai/medassist/refresh-session.md): Refreshes an expired session token to extend the session lifetime.
- [WebSocket API](https://developer.eka.care/api-reference/health-ai/medassist/websocket.md): Real-time communication with MedAssist through WebSocket connection
- [Overview](https://developer.eka.care/api-reference/health-ai/medassist/synapse/introduction.md): Add a Synapse AI medical assistant to any website, React app, or custom UI
- [Choose your integration](https://developer.eka.care/api-reference/health-ai/medassist/synapse/choose-integration.md): Decide between the embed widget, the React SDK, and the core SDK
- [Quickstart](https://developer.eka.care/api-reference/health-ai/medassist/synapse/embed/quickstart.md): Add the MedAssist widget to any website with one tag and a script
- [Customization & overrides](https://developer.eka.care/api-reference/health-ai/medassist/synapse/embed/customization.md): Every attribute, theme option, and config override for the embed widget
- [JavaScript API](https://developer.eka.care/api-reference/health-ai/medassist/synapse/embed/javascript-api.md): Configure the embed widget programmatically with EkaMedAssist.init()
- [Installation & setup](https://developer.eka.care/api-reference/health-ai/medassist/synapse/react/installation.md): Render the prebuilt MedAssist chat widget inside your React app
- [Configuration reference](https://developer.eka.care/api-reference/health-ai/medassist/synapse/react/configuration.md): Every option in MedAssistConfig
- [Theming & design system](https://developer.eka.care/api-reference/health-ai/medassist/synapse/react/theming.md): Brand the MedAssist widget with the Eka design system
- [Quickstart](https://developer.eka.care/api-reference/health-ai/medassist/synapse/core/quickstart.md): Build a custom MedAssist UI on the raw Synapse core SDK
- [Events](https://developer.eka.care/api-reference/health-ai/medassist/synapse/core/events.md): Subscribe to real-time events from the Synapse session
- [Tool calls & elicitation](https://developer.eka.care/api-reference/health-ai/medassist/synapse/core/tool-calls.md): Render the inputs the agent asks for and send results back
- [Voice & audio](https://developer.eka.care/api-reference/health-ai/medassist/synapse/core/voice.md): Record audio and run voice-mode conversations
- [API reference](https://developer.eka.care/api-reference/health-ai/medassist/synapse/core/api-reference.md): Methods, types, and enums of @eka-care/medassist-core
- [Introduction](https://developer.eka.care/api-reference/health-ai/medical-document-parsing/introduction.md)
- [Upload Report](https://developer.eka.care/api-reference/health-ai/medical-document-parsing/upload-report.md): Upload the image or PDF file
- [Parsed Report Result](https://developer.eka.care/api-reference/health-ai/medical-document-parsing/parsed-report-result.md): Use this API with the document_id to fetch results. This endpoint returns a JSON response that includes a detailed and structured parsed report.
- [Delete Document](https://developer.eka.care/api-reference/health-ai/medical-document-parsing/delete-document.md): This API is used to delete a document using a document ID.
- [Python](https://developer.eka.care/SDKs/backend/report-parsing-sdk.md): A Python SDK for parsing medical documents using Eka Care APIs
- [Java](https://developer.eka.care/SDKs/backend/report-parsing-sdk-java.md): A Java Spring Boot SDK for parsing medical documents using Eka Care APIs
- [Smart report webhook](https://developer.eka.care/api-reference/health-ai/medical-document-parsing/smart-report-webhook.md)
- [Pii webhook](https://developer.eka.care/api-reference/health-ai/medical-document-parsing/pii-webhook.md)
- [Classification webhook](https://developer.eka.care/api-reference/health-ai/medical-document-parsing/classification-webhook.md)
- [Medical Entity Codification](https://developer.eka.care/api-reference/health-ai/medical-entity-codification/overview.md): Map free-text medical entities to standardised ontology codes — SNOMED CT, LOINC, ICD-10-CM and Eka's medication database.
- [List Registry](https://developer.eka.care/api-reference/health-ai/medical-entity-codification/registry.md): Returns every ontology available for codification, the versions of each ontology, and the active indexes backing them. Use this to discover the exact `ontology` and `version` values to send to the linking endpoints.
- [Link Entity](https://developer.eka.care/api-reference/health-ai/medical-entity-codification/link-entity.md): Links a single free-text medical entity to candidate codes from the requested ontology. The `metadata` field carries ontology-specific hints — it is **strongly recommended for LOINC** (a unit can change the linked code) and **optional for medication**. SNOMED CT and ICD-10-CM Comprehend do not use `…
- [Link Entities (Batch)](https://developer.eka.care/api-reference/health-ai/medical-entity-codification/link-entity-batch.md): Links up to 5 free-text entities in a single call. All queries in a batch share the same `ontology`, `version`, `top_k` and `metadata`. The response contains one result block per query, in request order.
- [Search Drugs and Laboratory Tests](https://developer.eka.care/api-reference/medical-db/drugs-and-labs.md): This endpoint returns comprehensive information about pharmaceutical drugs and laboratory tests from the Eka medical database based on search query.
- [Search Symptoms and Diagnoses](https://developer.eka.care/api-reference/medical-db/symptoms-and-diagnosis.md): This endpoint returns comprehensive information about medical symptoms and diagnoses from the Eka medical database based on search query.
- [Overview](https://developer.eka.care/api-reference/user-app/abdm-connect/overview.md): Understand what ABDM is, who the key players are, and what you can build with EKA's ABDM Connect APIs and SDKs.
- [Error Code Mapping](https://developer.eka.care/api-reference/user-app/abdm-connect/errors.md)
- [Build a PHR App](https://developer.eka.care/api-reference/user-app/abdm-connect/phr/overview.md): End-to-end map of every EKA ABDM Connect API you need to build a Personal Health Record (PHR) application, in the order a patient journey needs them.
- [1 · ABHA Onboarding](https://developer.eka.care/api-reference/user-app/abdm-connect/phr/abha-onboarding.md): Create an ABHA address, log the patient in, and hold a live ABHA Gateway session.
- [2 · Profile Management](https://developer.eka.care/api-reference/user-app/abdm-connect/phr/profile.md): Read and update the patient's ABHA profile, run KYC, and render the ABHA card and QR code.
- [3 · Scan & Share](https://developer.eka.care/api-reference/user-app/abdm-connect/phr/scan-and-share.md): Let the patient scan a facility QR code to register instantly and receive a token number.
- [4 · Discover & Link Records](https://developer.eka.care/api-reference/user-app/abdm-connect/phr/discover-and-link.md): Find the patient's existing records at any ABDM-connected facility and link them to their ABHA address.
- [5 · Consents & Subscriptions](https://developer.eka.care/api-reference/user-app/abdm-connect/phr/consents.md): The patient's control panel: list, approve, deny and revoke consent requests, and set up auto-approval and the health locker.
- [6 · Fetch & Display Records](https://developer.eka.care/api-reference/user-app/abdm-connect/phr/records.md): List the patient's linked providers and care contexts, receive FHIR data, and let the patient upload their own documents.
- [7 · PHR Webhooks](https://developer.eka.care/api-reference/user-app/abdm-connect/phr/webhooks.md): Every asynchronous event a PHR app's cloud must handle, in one list.
- [Milestone 1](https://developer.eka.care/api-reference/user-app/abdm-connect/flows/m1.md): ABHA Creation and Login flows for ABDM integration.
- [Overview](https://developer.eka.care/api-reference/user-app/abdm-connect/registration/intro.md)
- [Generate OTP](https://developer.eka.care/api-reference/user-app/abdm-connect/enrollment/aadhaar/initiate-registration.md): This endpoint is used to initiate the Aadhaar registration process.
- [Resend OTP](https://developer.eka.care/api-reference/user-app/abdm-connect/enrollment/aadhaar/aadhaar-resend-otp.md): This endpoint is used to resend a otp for aadhaar registration process.
- [Verify OTP](https://developer.eka.care/api-reference/user-app/abdm-connect/enrollment/aadhaar/verify-otp.md): This endpoint is used to verify Aadhaar otp generated for registration using Aadhaar.
- [Mobile Resend OTP](https://developer.eka.care/api-reference/user-app/abdm-connect/enrollment/aadhaar/mobile-resend-otp.md): This endpoint is used to resend the mobile otp for aadhaar registration process.
- [Mobile Verify OTP](https://developer.eka.care/api-reference/user-app/abdm-connect/enrollment/aadhaar/mobile-verify.md): This API operates on a skip logic basis. If the mobile number provided in the second step differs from the one linked to the Aadhaar, this API will be used to verify the new mobile number.
- [Create](https://developer.eka.care/api-reference/user-app/abdm-connect/enrollment/aadhaar/create-abha.md): This API is used to create a new ABHA address
- [Auto Login](https://developer.eka.care/api-reference/user-app/abdm-connect/enrollment/aadhaar/auto-login.md): API for Auto login
- [Generate OTP](https://developer.eka.care/api-reference/user-app/abdm-connect/enrollment/mobile/init.md): This endpoint is used to initiate the registration process for a mobile number.
- [Resend OTP](https://developer.eka.care/api-reference/user-app/abdm-connect/enrollment/mobile/resend.md): This endpoint is used to resend a mobile registration request.
- [Verify OTP](https://developer.eka.care/api-reference/user-app/abdm-connect/enrollment/mobile/verify.md): This endpoint allows to verify a mobile otp.
- [Create](https://developer.eka.care/api-reference/user-app/abdm-connect/enrollment/mobile/create.md): This API is used to create a new ABHA address for the user.
- [Overview](https://developer.eka.care/api-reference/user-app/abdm-connect/enrollment/face-auth/intro.md): Authenticate users via Aadhaar-based facial recognition
- [Face Auth Init](https://developer.eka.care/api-reference/user-app/abdm-connect/enrollment/face-auth/face-auth-init.md): Face Auth endpoint is used to init face-auth endpoint.
- [Capture Face](https://developer.eka.care/api-reference/user-app/abdm-connect/enrollment/face-auth/face-auth-capture.md): Capture PID endpoint is used to capture face-auth pid.
- [Verify Face](https://developer.eka.care/api-reference/user-app/abdm-connect/enrollment/face-auth/face-auth-verify.md): Verify PID endpoint is used to verify face-auth pid.
- [Search Auth Methods](https://developer.eka.care/api-reference/user-app/abdm-connect/login/methods.md): Searches for available authentication methods.
- [Generate OTP](https://developer.eka.care/api-reference/user-app/abdm-connect/login/init.md): Generates an OTP for login. Supports login via Aadhaar number, mobile number, ABHA number, and ABHA address.
- [Verify OTP](https://developer.eka.care/api-reference/user-app/abdm-connect/login/verify.md): Verifies the login OTP. If logging in via ABHA address, this endpoint also completes the login process.
- [Login](https://developer.eka.care/api-reference/user-app/abdm-connect/login/login.md): Handles login via Aadhaar number, ABHA number, or mobile number.
- [Does Abha Address Exist](https://developer.eka.care/api-reference/user-app/abdm-connect/commons/does-health-id-exist.md): This API endpoint allows to check whether provided health id is already present in system.
- [Pincode details](https://developer.eka.care/api-reference/user-app/abdm-connect/commons/pincode-details.md): This API endpoint is used to fetch pincode details.
- [Suggest Abha Address](https://developer.eka.care/api-reference/user-app/abdm-connect/commons/suggest-abha-address.md): This API endpoint is used to fetch some suggested abha id that are available on the basis of user details.
- [Overview](https://developer.eka.care/api-reference/user-app/abdm-connect/profile/getting-started.md)
- [Search ABHA](https://developer.eka.care/api-reference/user-app/abdm-connect/profile/search/search.md): Search KYCed ABHA profiles using mobile number
- [ABHA QR Code](https://developer.eka.care/api-reference/user-app/abdm-connect/profile/cards/qr-code.md): Fetch the data for ABHA qr code display. Please cache these results locally. We do not recommend calling this API on every page load. Evict the cache when there is profile update.There is no fixed structure for this JSON; it can vary depending on the creation of ABHA. Generate…
- [ABHA card](https://developer.eka.care/api-reference/user-app/abdm-connect/profile/cards/abha-card.md): Fetch the ABHA card.Please cache these results locally. We do not recommend calling this API on every page load. Evict the cache when there is profile update.
- [Profile Details](https://developer.eka.care/api-reference/user-app/abdm-connect/profile/details/profile-details.md): Fetches the ABHA profile of the User. Please cache these results locally. We do not recommend calling this API on every page load. Evict the cache when there is profile update.
- [Update Profile](https://developer.eka.care/api-reference/user-app/abdm-connect/profile/details/update-profile.md): Name, gender and date of birth cannot be edited for a KYC verified ABHA
- [Delete Profile](https://developer.eka.care/api-reference/user-app/abdm-connect/profile/details/delete.md): This endpoint removes the specified ABHA profile along with all associated documents, vital records, and any other related data from the system.Please note that the ABHA metadata will remain in the ABDM system, as ABDM does not provide a delete option
- [Kyc init](https://developer.eka.care/api-reference/user-app/abdm-connect/profile/kyc/kyc-init.md): Request otp to initialise the KYC flow
- [Kyc resend](https://developer.eka.care/api-reference/user-app/abdm-connect/profile/kyc/kyc-resend.md): Resend otp for KYC
- [Kyc verify](https://developer.eka.care/api-reference/user-app/abdm-connect/profile/kyc/kyc-verify.md): Verify OTP to complete KYC
- [Overview](https://developer.eka.care/api-reference/user-app/abdm-connect/session/getting-started.md)
- [Status](https://developer.eka.care/api-reference/user-app/abdm-connect/session/status.md): Status of the user by the session.
- [Init](https://developer.eka.care/api-reference/user-app/abdm-connect/session/init.md): Generate mobile OTP for user session token
- [Verify](https://developer.eka.care/api-reference/user-app/abdm-connect/session/verify.md): Verify mobile OTP and get user session token
- [Overview](https://developer.eka.care/api-reference/user-app/abdm-connect/scan-and-share/getting-started.md)
- [Request to generate token](https://developer.eka.care/api-reference/user-app/abdm-connect/scan-and-share/phr-scan-share.md): Request to generate appointment token at the facility. Get the hip_id and counter_id by reading the QR code of the Hospital/Clinic. Use the device location for the location data
- [Get appointment token](https://developer.eka.care/api-reference/user-app/abdm-connect/scan-and-share/phr-scan-share-token.md): Get token number issued by the facility
- [On-Share](https://developer.eka.care/api-reference/user-app/abdm-connect/scan-and-share/scan-on-share.md): This API receives the Token Generated by the facility.
- [ABHA Address Created](https://developer.eka.care/api-reference/user-app/abdm-connect/webhooks/abha-created.md)
- [Locker Created](https://developer.eka.care/api-reference/user-app/abdm-connect/webhooks/locker-created.md)
- [Get Started](https://developer.eka.care/SDKs/web-sdk/abha-sdk/get-started.md): Complete implementation guide for the ABHA[Ayushman Bharat Digital Mission] SDK
- [Registration](https://developer.eka.care/SDKs/web-sdk/abha-sdk/abha-login-create.md): Complete implementation guide for the ABHA SDK to be used for ABHA Login or Create.
- [Profile KYC](https://developer.eka.care/SDKs/web-sdk/abha-sdk/abha-kyc.md): Complete implementation guide for the ABHA SDK to be used for ABHA KYC Verification Flow.
- [Scan & Share](https://developer.eka.care/SDKs/web-sdk/abha-sdk/abha-s&s.md): Complete implementation guide for the ABHA SDK to be used for ABHA Scan & Share Book Appointment Flow.
- [Custom Theming](https://developer.eka.care/SDKs/web-sdk/abha-sdk/abha-sdk-theme.md): Customize the ABHA SDK colors to match your application's branding
- [Milestone 2](https://developer.eka.care/api-reference/user-app/abdm-connect/flows/m2.md): Care Context Linking and Data Fetch flow for ABDM integration.
- [Overview](https://developer.eka.care/api-reference/user-app/abdm-connect/care-contexts/getting-started.md)
- [Encryption](https://developer.eka.care/api-reference/user-app/abdm-connect/care-contexts/ecdh-encryption.md): ECDH encryption for ABDM health data exchange using the open-source abdm-ecdh library.
- [Update public keyset](https://developer.eka.care/api-reference/user-app/abdm-connect/care-contexts/hiu-keys.md): API to update the HIU's public keyset.
- [Push care context data to HIU](https://developer.eka.care/api-reference/user-app/abdm-connect/care-contexts/data-on-fetch.md): Use this API to push encrypted FHIR data to the HIU after receiving the [`abha.hip_data_fetch`](/api-reference/user-app/abdm-connect/webhooks/hip-data-fetch) webhook.
- [Push FHIR parsing status](https://developer.eka.care/api-reference/user-app/abdm-connect/care-contexts/data-on-push.md): API for HIU to push care context FHIR parsing status
- [Get Linked Providers](https://developer.eka.care/api-reference/user-app/abdm-connect/care-contexts/providers/providers.md)
- [Get Linked CareContexts](https://developer.eka.care/api-reference/user-app/abdm-connect/care-contexts/records/records.md)
- [Care context linking](https://developer.eka.care/api-reference/user-app/abdm-connect/care-contexts/link/hip-linking.md): Use this API to link a care context to the patient's ABHA address. A care context represents a visit, test, or any logical grouping of health records.
- [Notify unlinked care contexts](https://developer.eka.care/api-reference/user-app/abdm-connect/care-contexts/records/notify.md): This API is used by HIP to notify the gateway when a new health record is ready to be shared with a user.
- [Care Context Discovery](https://developer.eka.care/api-reference/user-app/abdm-connect/care-contexts/discover/introduction.md)
- [Discover unlinked care-contexts](https://developer.eka.care/api-reference/user-app/abdm-connect/care-contexts/discover/discover.md): ABDM allows a user to find their health records from any health facility they have visited via the discovery process.
- [Initialise Linking](https://developer.eka.care/api-reference/user-app/abdm-connect/care-contexts/discover/link-init.md): Initialise the linking for discovered care context.
- [Confirm Linking](https://developer.eka.care/api-reference/user-app/abdm-connect/care-contexts/discover/link-confirm.md): Confirm linking for discovered care context
- [Discover On Care Contexts](https://developer.eka.care/api-reference/user-app/abdm-connect/care-contexts/discover/on_discover.md): This API is used to send unlinked care contexts to abdm.
- [Discover Link On Init](https://developer.eka.care/api-reference/user-app/abdm-connect/care-contexts/discover/link_on_init.md): This API is used by HIP to initiate the linking of unlinked health records (care contexts). HIP must send an OTP and provide details such as OTP expiry and other related information.
- [Discover Link On Confirm](https://developer.eka.care/api-reference/user-app/abdm-connect/care-contexts/discover/link_on_confirm.md): This API is used by HIP to confirm the linking of care contexts after OTP verification.
- [Overview](https://developer.eka.care/api-reference/user-app/abdm-connect/patient-requests/getting-started.md)
- [List requests](https://developer.eka.care/api-reference/user-app/abdm-connect/patient-requests/list-requests.md): API to list all the Subscriptions and Consent requests
- [Requests get details](https://developer.eka.care/api-reference/user-app/abdm-connect/patient-requests/requests-get-details.md)
- [Overview](https://developer.eka.care/api-reference/user-app/abdm-connect/providers/getting-started.md)
- [Get Provider Details](https://developer.eka.care/api-reference/user-app/abdm-connect/providers/provider.md): Fetches the Providers based on the HIP ID.
- [Search Providers](https://developer.eka.care/api-reference/user-app/abdm-connect/providers/search/providers.md): Fetches the List of Providers.
- [Care Context Linking Status](https://developer.eka.care/api-reference/user-app/abdm-connect/webhooks/link-care-context.md)
- [Scan and Share Token Received](https://developer.eka.care/api-reference/user-app/abdm-connect/webhooks/hip-scan-and-share.md)
- [Health Data Requested by HIU](https://developer.eka.care/api-reference/user-app/abdm-connect/webhooks/hip-data-fetch.md)
- [Health Data Received from HIP](https://developer.eka.care/api-reference/user-app/abdm-connect/webhooks/hiu-data-push.md)
- [Subscription Updated](https://developer.eka.care/api-reference/user-app/abdm-connect/webhooks/subscription-modify.md)
- [New Care Context Linked (Subscription)](https://developer.eka.care/api-reference/user-app/abdm-connect/webhooks/subscription-notify.md)
- [Discovery Request Received](https://developer.eka.care/api-reference/user-app/abdm-connect/webhooks/discover-care-context.md)
- [Link Initiation - Generate OTP](https://developer.eka.care/api-reference/user-app/abdm-connect/webhooks/discover-link-init.md)
- [Link Confirmation - Verify OTP](https://developer.eka.care/api-reference/user-app/abdm-connect/webhooks/discover-link-confirm.md)
- [Golang](https://developer.eka.care/SDKs/backend/go-sdk.md)
- [Milestone 3](https://developer.eka.care/api-reference/user-app/abdm-connect/flows/m3.md): Consent management and health data retrieval flow for ABDM integration.
- [Overview](https://developer.eka.care/api-reference/user-app/abdm-connect/consents/getting-started.md)
- [Consent create](https://developer.eka.care/api-reference/user-app/abdm-connect/consents/consent-create.md)
- [Consent list](https://developer.eka.care/api-reference/user-app/abdm-connect/consents/consent-list.md)
- [Consent details](https://developer.eka.care/api-reference/user-app/abdm-connect/consents/consent-details.md)
- [Consent approve](https://developer.eka.care/api-reference/user-app/abdm-connect/consents/consent-approve.md): This endpoint is used to approve the consent
- [Consent deny](https://developer.eka.care/api-reference/user-app/abdm-connect/consents/consent-deny.md): This endpoint is used to deny the consent
- [Consent revoke](https://developer.eka.care/api-reference/user-app/abdm-connect/consents/consent-revoke.md): This endpoint is used to revoke the consent
- [Get status](https://developer.eka.care/api-reference/user-app/abdm-connect/consents/auto-approval/get-status.md): Fetch the auto approval policy settings
- [Update auto approval policy](https://developer.eka.care/api-reference/user-app/abdm-connect/consents/auto-approval/update-auto-approval-policy.md): Update the auto approval policy settings
- [Consent update](https://developer.eka.care/api-reference/user-app/abdm-connect/webhooks/consent-update.md)
- [Get Started](https://developer.eka.care/SDKs/web-sdk/consent-management/get-started.md): Embed ABDM medical records consent management into your application
- [Milestone 4](https://developer.eka.care/api-reference/user-app/abdm-connect/flows/m4.md): Healthcare Professional Registry (HPR), Health Facility Registry (HFR), and Onboarding flows for ABDM integration.
- [Overview](https://developer.eka.care/api-reference/user-app/abdm-connect/nhpr-abdm/getting-started.md)
- [Get Aadhaar OTP](https://developer.eka.care/api-reference/user-app/abdm-connect/nhpr-abdm/hpr/get-aadhar-otp.md): Get Aadhar OTP
- [Verify Aadhaar OTP](https://developer.eka.care/api-reference/user-app/abdm-connect/nhpr-abdm/hpr/verify-aadhar-otp.md): Verify Aadhar OTP
- [Verify Mobile](https://developer.eka.care/api-reference/user-app/abdm-connect/nhpr-abdm/hpr/verify-mobile.md): Verify Aadhaar Linked Mobile
- [Get HPR Info](https://developer.eka.care/api-reference/user-app/abdm-connect/nhpr-abdm/hpr/check-hpr-exist.md): Check if HPR ID Exists
- [Suggest IDs](https://developer.eka.care/api-reference/user-app/abdm-connect/nhpr-abdm/hpr/suggest-ids.md): Get Suggested HPR IDs
- [Create HPR](https://developer.eka.care/api-reference/user-app/abdm-connect/nhpr-abdm/hpr/create-hpr.md): Create HPR ID
- [Get Mobile OTP](https://developer.eka.care/api-reference/user-app/abdm-connect/nhpr-abdm/hpr/get-mobile-otp.md): Generate Mobile OTP
- [Verify Mobile OTP](https://developer.eka.care/api-reference/user-app/abdm-connect/nhpr-abdm/hpr/verify-mobile-otp.md): Verify Mobile OTP
- [Check If HPR is Available](https://developer.eka.care/api-reference/user-app/abdm-connect/nhpr-abdm/hpr/check-hpr-available.md): Check HPR ID Availability
- [Search HFR](https://developer.eka.care/api-reference/user-app/abdm-connect/nhpr-abdm/hfr/search-facility.md): Search Facility
- [Onboard HFR](https://developer.eka.care/api-reference/user-app/abdm-connect/nhpr-abdm/hfr/onboard-facility.md): Onboard Facility
- [Link HFR](https://developer.eka.care/api-reference/user-app/abdm-connect/nhpr-abdm/hfr/link-facility.md): Link a facility to the ABDM Bridge
- [Facility Onboarding](https://developer.eka.care/api-reference/user-app/abdm-connect/nhpr-abdm/onboarding-overview.md): Onboard your ABDM-registered healthcare facility to the Eka system
- [Onboard facility](https://developer.eka.care/api-reference/user-app/abdm-connect/nhpr-abdm/onboarding.md): Onboard facility
- [Get Started](https://developer.eka.care/SDKs/web-sdk/nhpr-sdk/get-started.md): Complete implementation guide for the NHPR (Health Professional Registry) SDK
- [Overview](https://developer.eka.care/api-reference/user-app/abdm-connect/blood-bank/getting-started.md)
- [Search Blood Banks](https://developer.eka.care/api-reference/user-app/abdm-connect/blood-bank/state-district.md): User can search blood banks using State & District wise.
- [Get Blood Banks](https://developer.eka.care/api-reference/user-app/abdm-connect/blood-bank/get-blood-banks.md): User can get blood banks.
- [Overview](https://developer.eka.care/api-reference/user-app/abdm-connect/scan-and-pay/getting-started.md)
- [Open Orders](https://developer.eka.care/api-reference/user-app/abdm-connect/scan-and-pay/open-orders.md): Share patient profile to get open orders.
- [Get Open Orders](https://developer.eka.care/api-reference/user-app/abdm-connect/scan-and-pay/get-open-orders.md): Retrieve open orders by request ID.
- [Patient Select](https://developer.eka.care/api-reference/user-app/abdm-connect/scan-and-pay/patient-select.md): To get payment link for selected Open Order with intent - 'PAYMENT_ORDER'
- [Get Patient Select Details](https://developer.eka.care/api-reference/user-app/abdm-connect/scan-and-pay/get-patient-select.md): Retrieve open orders by request ID.
- [Get Transaction Details](https://developer.eka.care/api-reference/user-app/abdm-connect/scan-and-pay/get-transaction-details.md): Retrieve open orders by request ID.
- [Search doctors](https://developer.eka.care/api-reference/user-app/abdm-connect/phys-cons/search-doctors.md): This api is used to search for doctors.
- [Get doctors](https://developer.eka.care/api-reference/user-app/abdm-connect/phys-cons/get-doctors.md): Fetches a list of doctors matching the given search criteria.
- [Search slots](https://developer.eka.care/api-reference/user-app/abdm-connect/phys-cons/search-slots.md): This API is used to search for available consultation slots for booking.
- [Get slots](https://developer.eka.care/api-reference/user-app/abdm-connect/phys-cons/get-slots.md): Fetches the list of a doctor available consultation slots.
- [Init](https://developer.eka.care/api-reference/user-app/abdm-connect/phys-cons/init.md): This api is used to Initiate the Booking.
- [Get init](https://developer.eka.care/api-reference/user-app/abdm-connect/phys-cons/get-init.md): Fetch initiation response for a physical consultation, including terms and conditions, payment modes, and pricing details.
- [Confirm](https://developer.eka.care/api-reference/user-app/abdm-connect/phys-cons/confirm.md): Confirm a physical consultation booking.
- [Get confirm](https://developer.eka.care/api-reference/user-app/abdm-connect/phys-cons/get-confirm.md): Retrieve booking confirmation details, including the OTP that must be presented to the doctor before consultation.
- [Order status](https://developer.eka.care/api-reference/user-app/abdm-connect/phys-cons/order-status.md)
- [Get order status](https://developer.eka.care/api-reference/user-app/abdm-connect/phys-cons/get-order-status.md)
- [Cancel](https://developer.eka.care/api-reference/user-app/abdm-connect/phys-cons/cancel.md): Cancel a physical consultation booking.
- [Get cancel](https://developer.eka.care/api-reference/user-app/abdm-connect/phys-cons/get-cancel.md): Retrieve the cancellation status of a physical consultation booking.
- [Update](https://developer.eka.care/api-reference/user-app/abdm-connect/phys-cons/update.md): Update the details of a physical consultation appointment.
- [Search doctors](https://developer.eka.care/api-reference/user-app/abdm-connect/webhooks/search-doctors.md)
- [Search slots](https://developer.eka.care/api-reference/user-app/abdm-connect/webhooks/search-slots.md)
- [Booking init](https://developer.eka.care/api-reference/user-app/abdm-connect/webhooks/booking-init.md)
- [Booking confirm](https://developer.eka.care/api-reference/user-app/abdm-connect/webhooks/booking-confirm.md)
- [Booking status](https://developer.eka.care/api-reference/user-app/abdm-connect/webhooks/booking-status.md)
- [Booking cancel](https://developer.eka.care/api-reference/user-app/abdm-connect/webhooks/booking-cancel.md)
- [Actors](https://developer.eka.care/api-reference/doc-tool/Actors/actors.md)
- [Before you begin](https://developer.eka.care/api-reference/doc-tool/Instructions/before-you-begin.md)
- [Getting started](https://developer.eka.care/api-reference/doc-tool/patient-registration-api/getting-started.md)
- [Add Patient to Directory](https://developer.eka.care/api-reference/doc-tool/patient-registration-api/add-patient-to-directory.md): This functionality enables the addition of new patient records to a business' directory. Users can provide necessary details such as personal information, contact details, and medical history to create a new patient profile.
- [Search Patient profiles by mobile number](https://developer.eka.care/api-reference/doc-tool/patient-registration-api/search-patient-by-mobile.md): This API provides functionality to get all profiles of patient by their mobile number in business' directory.
- [Get patient details by profile id](https://developer.eka.care/api-reference/doc-tool/patient-registration-api/get-patient-details-by-id.md): This API provides functionality to get details of a patient by their Eka profile id, from a business' directory. The patient should have been previously added to the business directory for this API to return the patient's details.
- [Update Patient Details](https://developer.eka.care/api-reference/doc-tool/patient-registration-api/update-patient-details-api.md): Thi API provides functionality to update patient details for the registered patients.
- [Getting started](https://developer.eka.care/api-reference/doc-tool/patient-directory-apis/getting-started.md)
- [Create a patient profile](https://developer.eka.care/api-reference/doc-tool/patient-directory-apis/add-patient.md): Allows businesses to add new patient record by capturing personal, contact, and medical information.
- [Search patient profiles](https://developer.eka.care/api-reference/doc-tool/patient-directory-apis/search-patient.md): **Global Search is exclusive to specific workspaces only. Please reach out to support.**
- [Retrieve patient profile](https://developer.eka.care/api-reference/doc-tool/patient-directory-apis/retrieve-patient-details.md)
- [Update patient profile details](https://developer.eka.care/api-reference/doc-tool/patient-directory-apis/update-patient-details.md): Payload for updating patient profile.
- [Archive patient profile](https://developer.eka.care/api-reference/doc-tool/patient-directory-apis/delete-patient.md): **Note:** The patient profile is not deleted permanently — it is only archived. Archived profiles can still be retrieved using the `arc=true` query parameter in the retrieve API.
- [List patient profiles](https://developer.eka.care/api-reference/doc-tool/patient-directory-apis/patients-list-minified.md): Retrieves a paginated list of patient profiles.
- [Retrieve patient profiles by mobile number](https://developer.eka.care/api-reference/doc-tool/patient-directory-apis/retrieve-patients-by-mobile.md): Retrieves patient profiles using the mobile number in a workspace. The mobile number must be in the format `+`.
- [Retrieve patient profile by username](https://developer.eka.care/api-reference/doc-tool/patient-directory-apis/retrieve-patient-by-username.md): Retrieves patient profile using username in a workspace.
- [Retrieve EMR user profile](https://developer.eka.care/api-reference/doc-tool/patient-directory-apis/retrieve-emr-user.md): Retrieves an EMR user profile by OID.
- [Update EMR user profile](https://developer.eka.care/api-reference/doc-tool/patient-directory-apis/update-emr-user.md): Updates an EMR user profile with validated and normalized data.
- [Trinity Profiles SDK (TypeScript)](https://developer.eka.care/api-reference/doc-tool/patient-directory-sdks/patient-directory-ts-sdk.md): Type-safe SDK for managing patient profiles through the Trinity API.
- [Getting started](https://developer.eka.care/api-reference/doc-tool/doctor-and-clinic-api/getting-started.md)
- [Get Clinic and Doctor details](https://developer.eka.care/api-reference/doc-tool/doctor-and-clinic-api/get-clinic-and-doctor-details.md): ### Overview The Get Clinic and Doctor Details API provides a comprehensive list of clinics and doctors associated with those clinics for a business. This API is designed to retrieve detailed information about clinics, the doctors working at each clinic, and the overarching business entity. ### Endp…
- [Get Doctor profile](https://developer.eka.care/api-reference/doc-tool/doctor-and-clinic-api/get-doctor-profile.md): ### Overview This API endpoint is used to retrieve detailed information about a specific doctor using their unique identifier. The response includes comprehensive information about the doctor, such as personal details, specializations, and associated clinics. ### Request Parameters
- [Get Clinic details](https://developer.eka.care/api-reference/doc-tool/doctor-and-clinic-api/get-clinic-details.md): ### Overview This API endpoint retrieves detailed information about a specific clinic using its unique identifier. ### Endpoint **URL:** `{{HOST}}/dr/v1/business/clinic/{{clinic_id}}` **Method:** GET ### Request Parameters | Parameter | Type | Description | Required | | --- | --- | --- | --- | | cli…
- [Get Doctor services](https://developer.eka.care/api-reference/doc-tool/doctor-and-clinic-api/get-doc-service.md): This API response returns a list of medical services offered by a specific doctor, including details like service name, duration, booking options, and fees. Each service specifies whether it supports pre-pay or post-pay, along with the delivery mode (e.g., in-clinic or teleconsultation). The data he…
- [Get All HIP Users of a Business](https://developer.eka.care/api-reference/doc-tool/user-apis/get-all-users.md): This API retrieves the list of all HIP users associated with a business. The response includes each user's details along with their linked doctors and clinics. > _Use this API to fetch all HIP users for a business account in one call._
- [Get HIP User Details by ID](https://developer.eka.care/api-reference/doc-tool/user-apis/get-user-by-id.md): This API retrieves detailed information about a specific HIP user registered under a business. The response includes the user's personal details, assigned doctors, and associated clinics. > _Use this API to get complete profile details of a single HIP user by their Eka user ID._
- [Get Workspace Information](https://developer.eka.care/api-reference/doc-tool/business-api/get-business-info.md): ### Overview The Get Workspace Information API retrieves basic information about a business including the business ID and business name. This API is designed to provide essential business details for authenticated requests. ### Endpoint **URL:** `{{HOST}}/cdr/v1/get_business_info`
- [Create Doctor Profile](https://developer.eka.care/api-reference/doc-tool/onboarding-apis/onboard-doctor.md): ### Overview Create a new doctor profile for your business. This endpoint lets you register a doctor with their personal details, specializations, qualifications, and profile image.
- [List Doctors](https://developer.eka.care/api-reference/doc-tool/onboarding-apis/list-doctors.md): ### Overview Retrieve a list of all doctors registered for your business. Each entry returns the doctor's basic profile, primary specialisation, partner ID, and the clinics they are associated with.
- [Get Doctor by ID](https://developer.eka.care/api-reference/doc-tool/onboarding-apis/get-doctor.md): ### Overview Retrieve a single doctor's profile using either the Eka ID or the partner-provided ID.
- [Update Doctor](https://developer.eka.care/api-reference/doc-tool/onboarding-apis/update-doctor.md): ### Overview Update an existing doctor's profile. Only the fields included in the request body will be updated; all fields are optional.
- [Delete Doctor](https://developer.eka.care/api-reference/doc-tool/onboarding-apis/delete-doctor.md): ### Overview Soft-delete a doctor by their Eka ID or partner-provided ID. Once deleted, the doctor will no longer appear in list or get responses.
- [Create Clinic](https://developer.eka.care/api-reference/doc-tool/onboarding-apis/onboard-clinic.md): ### Overview The Create Clinic API allows you to register a new clinic for your business, including its name, address, pincode, contact number, city, state, and assigned doctors.
- [List Clinics](https://developer.eka.care/api-reference/doc-tool/onboarding-apis/list-clinics.md): ### Overview Retrieve a list of all clinics registered for your business. Each entry includes basic clinic details and the doctors associated with that clinic.
- [Get Clinic by ID](https://developer.eka.care/api-reference/doc-tool/onboarding-apis/get-clinic.md): ### Overview Retrieve a single clinic's details using either the Eka ID or the partner-provided ID.
- [Update Clinic](https://developer.eka.care/api-reference/doc-tool/onboarding-apis/update-clinic.md): ### Overview Update an existing clinic. Only the fields included in the request body will be updated; all fields are optional.
- [Delete Clinic](https://developer.eka.care/api-reference/doc-tool/onboarding-apis/delete-clinic.md): ### Overview Soft-delete a clinic by Eka ID or partner-provided ID. Deleted clinics no longer appear in list or get responses.
- [Create Eka User](https://developer.eka.care/api-reference/doc-tool/onboarding-apis/onboard-ekauser.md): ### Overview Create a new Eka User (HIP User) for your business. This endpoint lets you register a user with their personal details and assign them to specific doctors and clinics.
- [List Eka Users](https://developer.eka.care/api-reference/doc-tool/onboarding-apis/list-ekausers.md): ### Overview Retrieve a list of all Eka Users (HIP Users) registered for your business. Each entry includes the user's profile, role, seat type, and the doctors and clinics they are associated with.
- [Get Eka User by ID](https://developer.eka.care/api-reference/doc-tool/onboarding-apis/get-ekauser.md): ### Overview Retrieve a single Eka User's profile using either the Eka ID or the partner-provided ID.
- [Update Eka User](https://developer.eka.care/api-reference/doc-tool/onboarding-apis/update-ekauser.md): ### Overview Update an existing Eka User. Only the fields included in the request body will be updated; all fields are optional.
- [Delete Eka User](https://developer.eka.care/api-reference/doc-tool/onboarding-apis/delete-ekauser.md): ### Overview Soft-delete an Eka User by Eka ID or partner-provided ID. Deleted users no longer appear in list or get responses.
- [Getting started](https://developer.eka.care/api-reference/doc-tool/appointment-api/getting-started.md)
- [Get Appointment Slots](https://developer.eka.care/api-reference/doc-tool/appointment-api/get-appointment-slots.md): This API is the first step in booking appointment slot for a patient at a doctor's clinic
- [Book Appointment Slot](https://developer.eka.care/api-reference/doc-tool/appointment-api/book-appointment-slot.md): This API is used to book an appointment slot for a patient based on the available slots retrieved from the `get appointment slots` API.
- [Get Appointment Details](https://developer.eka.care/api-reference/doc-tool/appointment-api/get-appointment-details.md)
- [Update Appointment](https://developer.eka.care/api-reference/doc-tool/appointment-api/update-appointment.md): ### Overview
- [Update Appointment V2](https://developer.eka.care/api-reference/doc-tool/appointment-api/update-appointment-v2.md): ### Overview
- [Parked Appointment](https://developer.eka.care/api-reference/doc-tool/appointment-api/parked-appointment.md): ### Overview
- [Complete Appointment](https://developer.eka.care/api-reference/doc-tool/appointment-api/complete-appointment.md): ### Overview
- [Cancel Appointment](https://developer.eka.care/api-reference/doc-tool/appointment-api/cancel-appointment.md): ### Overview
- [Get Appointments](https://developer.eka.care/api-reference/doc-tool/appointment-api/get-appointments-by-date.md)
- [No-Show Appointment](https://developer.eka.care/api-reference/doc-tool/appointment-api/change-status.md): ### Overview
- [Confirm Follow-Up Appointment](https://developer.eka.care/api-reference/doc-tool/appointment-api/confirm-follow-up-appointment.md): ### Overview
- [Reschedule Appointment](https://developer.eka.care/api-reference/doc-tool/appointment-api/reschedule-appointment.md): ### Overview
- [Get Transaction Status](https://developer.eka.care/api-reference/doc-tool/payment-api/get-transaction-status.md)
- [Get Prescription details](https://developer.eka.care/api-reference/doc-tool/prescription-api/get-prescription-details.md): This API retrieves comprehensive details of a prescription created by a doctor. It provides a rich set of data encompassing patient history, diagnosis, medications, lab tests, and various other clinical elements. The response includes:
- [Get IPD Admission](https://developer.eka.care/api-reference/doc-tool/ipd-api/admission-details.md): ### Overview
- [Create IPD Admission](https://developer.eka.care/api-reference/doc-tool/ipd-api/admission-create.md): ### Overview
- [Send Notification](https://developer.eka.care/api-reference/doc-tool/notify/notify.md): This API allows partners to send notifications to users. The notifications can include a title, body, image URL, link, and a param if provided. The API supports different platform flavors such as Android, iOS, iPad and Web.
- [Create appointment](https://developer.eka.care/api-reference/doc-tool/post_webhooks/add-appointment-webhook.md): When an appointment is created, a webhook event is sent to registered webhooks with details about the appointment, including the appointment ID, status, doctor ID, patient ID, and event type.
- [Update appointment](https://developer.eka.care/api-reference/doc-tool/post_webhooks/update-appointment-webhook.md): When an appointment is updated, a webhook event is sent to registered webhooks with details about the appointment, including the appointment ID, status, doctor ID, patient ID, and event type.
- [Assessment Taken](https://developer.eka.care/api-reference/doc-tool/post_webhooks/assessment-taken-webhook.md): When an assessment linked to the appointment is completed, a webhook event is sent to registered webhooks with details about the appointment, including the appointment ID, status, doctor ID, patient ID, and event type.
- [Status changed](https://developer.eka.care/api-reference/doc-tool/post_webhooks/status-change-webhook.md): When status of an appointment changes, a webhook event is sent to registered webhooks with details about the appointment, including the appointment ID, status, doctor ID, patient ID, and event type.
- [Doctor Joined Video Call](https://developer.eka.care/api-reference/doc-tool/post_webhooks/appointment-tele-dr-joined-webhook.md): This webhook is triggered when a doctor joins a scheduled video consultation.
- [Appointment Reminder (Instant)](https://developer.eka.care/api-reference/doc-tool/post_webhooks/appointment-reminder-instant-webhook.md): This webhook is triggered to send an instant reminder for an upcoming appointment. Unlike the standard reminder which is scheduled in advance, this reminder event is sent immediately. The receiving system can use this to trigger instant alerts to the patient or doctor.
- [Follow-up Appointment Reminder (Instant)](https://developer.eka.care/api-reference/doc-tool/post_webhooks/appointment-followup-reminder-instant-webhook.md): This webhook is triggered to send an instant reminder for an upcoming follow-up appointment. Unlike the standard follow-up reminder which is scheduled in advance, this reminder event is send immediately. The receiving system can use this to trigger instant follow-up visit alerts to the patient or do…
- [Vaccination Reminder](https://developer.eka.care/api-reference/doc-tool/post_webhooks/vaccination-reminder-webhook.md): This webhook is triggered when a vaccination reminder is sent for a patient. It notifies the registered endpoint with vaccination details so the receiving system can send appropriate reminders to the patient or doctor.
- [Prescription Created Event](https://developer.eka.care/api-reference/doc-tool/post_webhooks/prescription-webhook.md): When a prescription is created or modified, a webhook event is sent to registered webhooks with details about the prescription, including the prescription ID, visit ID, doctor ID, patient ID, and event type.
- [Prescription Communication Event](https://developer.eka.care/api-reference/doc-tool/post_webhooks/prescription-communication-webhook.md): This webhook is triggered when a user performs an on-demand "Send Rx" action from the tool, sharing a prescription with the patient. The registered endpoint receives details about the prescription that was communicated, including the prescription ID, prescription URL, doctor, patient and appointment…
- [Doctor Events](https://developer.eka.care/api-reference/doc-tool/post_webhooks/doctor-webhook.md): When a Doctor event occurs (such as the start of a practice), a webhook event is sent to registered webhooks with details about the schedule, including the doctor ID, partner doctor ID, and event time. The receiver can use the details from the webhook event to update or manage schedules in the syste…
- [Google Review Automatic Event](https://developer.eka.care/api-reference/doc-tool/post_webhooks/google-review-webhook.md): When a prescription ends then automatically a webhook is sent to the registered endpoint containing the Doctor ID, Google review link, and Patient ID. The receiving system can use these details to update or manage Google review information as needed.
- [Google Review Manual Event](https://developer.eka.care/api-reference/doc-tool/post_webhooks/google-review-manual-webhook.md): When a Google review request is manually triggered through doctor platform, a webhook is sent to the registered endpoint containing the Appointment ID, Doctor ID, Patient ID, Clinic ID, and Google review link. The receiving system can use these details to update or manage Google review information a…
- [Consent Form Events](https://developer.eka.care/api-reference/doc-tool/post_webhooks/mcert-webhook.md): When a consent form or medical certificate is created or updated, a webhook is sent to the registered endpoint containing the Doctor Id, Patient Id, Consent form url, **type(represents whether it is a medical certificate or consent form)** etc. The receiving system can use these details as per their…
- [Receipt Events](https://developer.eka.care/api-reference/doc-tool/post_webhooks/receipt-webhook.md): When a Receipt is created, updated or deleted, a webhook is sent to the registered endpoint containing the Doctor Id, Patient Id, Clinic Id etc. The receiving system can use these details as per their need.
- [Payment Link Requested](https://developer.eka.care/api-reference/doc-tool/post_webhooks/payment-link-webhook.md): When a payment link is requested against an appointment, a webhook event is sent to the registered endpoint containing the appointment ID, doctor ID, patient ID, net amount and the payment checkout URL.
- [IPD Admission](https://developer.eka.care/api-reference/doc-tool/post_webhooks/ipd-admissions.md): When an IPD (In-Patient Department) admission is created or updated, a webhook event is sent to registered webhooks with the full admission details, including the patient, attending doctor, facility, department, bed, category, rate plan, insurance and billing information.
- [IPD Admission Event](https://developer.eka.care/api-reference/doc-tool/post_webhooks/ipd-admissions-events.md): When an event occurs against an IPD admission (such as a clearance, stage change or other workflow action), a webhook event is sent to registered webhooks describing the action that was performed.
- [IPD Admission Clearance](https://developer.eka.care/api-reference/doc-tool/post_webhooks/ipd-admissions-clearances.md): When a clearance is created or updated against an IPD admission (for example a pharmacy, billing or housekeeping clearance), a webhook event is sent to registered webhooks with the clearance status and details.
- [IPD Admission Estimate](https://developer.eka.care/api-reference/doc-tool/post_webhooks/ipd-admissions-estimates.md): When a cost estimate line item is created or updated against an IPD admission, a webhook event is sent to registered webhooks with the estimate details, including the service, rate, quantity and any discount applied.
- [IP Allowlisting for Clients](https://developer.eka.care/api-reference/doc-tool/ip-allowlisting-for-clients.md): Allowlisting and endpoint information to access Eka Care EMR
- [Overview](https://developer.eka.care/api-reference/knowledge-base/overview.md)
- [Search Protocols](https://developer.eka.care/api-reference/knowledge-base/protocols/search.md): This endpoint returns pages from the protocols based on the query, publishers and tag.
- [Get all Publishers](https://developer.eka.care/api-reference/knowledge-base/protocols/publishers.md): This endpoint returns a list of all protocols publishers
- [Search Medications](https://developer.eka.care/api-reference/knowledge-base/medications/search.md): This endpoint returns suggested/similar drugs from the Eka medical database for the given parameters - drug name, generics, form or volume. Suggestions are ranked based on similarity and also popularity (custom eka metric) of the medicine
- [Get Generic (pharmacology) Information](https://developer.eka.care/api-reference/knowledge-base/medications/pharmacology.md)
- [SNOMED Linking (Deprecated)](https://developer.eka.care/api-reference/knowledge-base/linking/snomed.md): **Deprecated.** Use `POST /med-link/nel/link` from the Medical Entity Codification API instead — see the [Link Entity](/api-reference/health-ai/medical-entity-codification/link-entity) docs. This endpoint remains operational for existing integrations.
- [Overview](https://developer.eka.care/api-reference/user-app/records/create-overview.md)
- [Step 1: Upload Record](https://developer.eka.care/api-reference/user-app/records/obtain-authorization.md): Generate a presigned URL that allows you to securely upload a document to the server. This URL can be used to upload the document directly without needing additional authentication or authorization steps.
- [Step 2: Upload Record](https://developer.eka.care/api-reference/user-app/records/upload-records.md)
- [Overview](https://developer.eka.care/api-reference/user-app/records/read-documents.md)
- [Describes a document](https://developer.eka.care/api-reference/user-app/records/describe-record.md): Once you retrieve a list of all documents with their corresponding IDs, you can use this endpoint to get more details about a specific document.
- [List Documents](https://developer.eka.care/api-reference/user-app/records/list-records.md): To get the list of all the records for a given authenticated user.
- [Retrieve health records](https://developer.eka.care/api-reference/user-app/records/retrieve-health-records.md): Retrieve a health record based on the given identifier, hip_id, and health_id in nrces FHIR json format.
- [Sends a refresh event to the origin](https://developer.eka.care/api-reference/user-app/records/send-refresh.md): This endpoint triggers a refresh event for the specified document, prompting the origin to update its state.
- [Overview](https://developer.eka.care/api-reference/user-app/records/update_overview.md)
- [Update Document](https://developer.eka.care/api-reference/user-app/records/update-document.md): This API is used to update the document.
- [Overview](https://developer.eka.care/api-reference/user-app/records/delete_overview.md)
- [Delete a document](https://developer.eka.care/api-reference/user-app/records/delete-document.md): This API is used to delete a document using a document ID.
- [Create Case](https://developer.eka.care/api-reference/user-app/records/create-case.md): This endpoint creates a new medical case.
- [Update Case](https://developer.eka.care/api-reference/user-app/records/update-case.md): This endpoint allows updating details of an existing medical case using the case ID.
- [List Cases](https://developer.eka.care/api-reference/user-app/records/list-case.md): This endpoint returns a list of all cases. Results are always ordered by ascending value of `updated_at`.
- [Delete Case](https://developer.eka.care/api-reference/user-app/records/delete-case.md): This endpoint allows deleting a case using the case ID.
- [IOS sdk](https://developer.eka.care/api-reference/user-app/records/SDKs/iOS-sdk.md)
- [Get Started](https://developer.eka.care/SDKs/web-sdk/mr-sdk/get-started.md): Complete implementation guide for the Medical Records Web SDK
- [Records](https://developer.eka.care/SDKs/web-sdk/mr-sdk/records.md): Upload, list, group, download, edit and delete medical documents with the Medical Records Web SDK
- [Cases](https://developer.eka.care/SDKs/web-sdk/mr-sdk/cases.md): Organise medical records into cases (folders) with the Medical Records Web SDK
- [Offline & Sync](https://developer.eka.care/SDKs/web-sdk/mr-sdk/offline-and-sync.md): Offline support, background sync, reactive UI updates, logging and Electron setup for the Medical Records Web SDK
- [Record refresh webhook](https://developer.eka.care/api-reference/user-app/records/record-refresh-webhook.md)
- [Record uploaded webhook](https://developer.eka.care/api-reference/user-app/records/record-uploaded-webhook.md)
- [Add Device](https://developer.eka.care/api-reference/user-app/notifications/add-device.md): Call to add or register a device for notifications. This endpoint allows clients to register a device by providing its details such as device ID, FCM ID, app version, and other relevant information. The registered device will be used to send notifications. The request body must contain the device pa…
- [Delete Device](https://developer.eka.care/api-reference/user-app/notifications/delete-device.md): To be called when the device is logged out or uninstalled. This endpoint allows clients to remove a registered device by specifying its device ID in the header. Upon successful deletion, the device will no longer receive notifications. The `device-id` parameter in the header is required.
- [Add FCM Credentials](https://developer.eka.care/api-reference/user-app/notifications/fcm-creds.md): Store FCM credentials. This endpoint allows clients to store Firebase Cloud Messaging (FCM) credentials by providing the service account key details. The stored credentials will be used for sending notifications to the registered devices. The request body must contain the FCM payload information.
- [Update Patient Vitals and Link to ABHA](https://developer.eka.care/api-reference/user-app/vitals/vitals.md): Update the vitals data for a specific patient using the transaction ID. It processes the data and links it to the ABHA (Ayushman Bharat Health Account) if requested. Request body must include valid list of vitals.
- [Vital information table](https://developer.eka.care/api-reference/user-app/vitals/vital-information-table.md)
- [Right to access](https://developer.eka.care/api-reference/user-app/webhook/right-to-access.md)
- [Request User Data](https://developer.eka.care/api-reference/user-app/privacy/right-to-access.md): This endpoint prepares the user data. After a 202 response from this API, the client will receive the user data via a webhook.
- [Overview](https://developer.eka.care/ekascribe/overview.md): EkaScribe turns clinical conversations into structured medical notes — via a simple session-based API
- [Build with AI (CLAUDE.md)](https://developer.eka.care/ekascribe/api-integration.md): Drop this file into your project and ask Claude, Cursor or any coding agent to build the EkaScribe flow for you
- [EkaScribe TypeScript SDK](https://developer.eka.care/ekascribe/sdks/ekascribe-ts-sdk.md): Record consultations in the browser and get structured medical notes back, with a prebuilt widget and session/document utilities.
- [MedScribe Alliance SDK (TypeScript)](https://developer.eka.care/ekascribe/sdks/TS-sdk.md): Record in the browser and get structured medical notes back — the open MedScribe Alliance Protocol SDK for TypeScript.
- [Python SDK](https://developer.eka.care/ekascribe/sdks/scribe-python-sdk.md): Turn medical audio into structured notes in a few lines of Python — the MedScribeAlliance Protocol SDK.
- [Python SDK (Deprecated)](https://developer.eka.care/ekascribe/sdks/python-sdk.md)
- [Java SDK](https://developer.eka.care/ekascribe/sdks/java-sdk.md)
- [Android SDK](https://developer.eka.care/ekascribe/sdks/android-sdk.md)
- [iOS SDK](https://developer.eka.care/ekascribe/sdks/ios-sdk.md)
- [Quickstart](https://developer.eka.care/ekascribe/quickstart.md): From audio to a structured clinical note in five API calls
- [Authenticate & Try the APIs](https://developer.eka.care/ekascribe/authenticate-and-try.md): Paste your client credentials once and call every EkaScribe API live from these docs
- [MedScribe Alliance Protocol](https://developer.eka.care/ekascribe/api-reference/protocol/overview.md): The open protocol every EkaScribe API is built on
- [Discovery](https://developer.eka.care/ekascribe/api-reference/protocol/discovery.md): Public, unauthenticated endpoint that advertises the service's protocol version, supported authentication methods, audio capabilities, available models and supported languages. Clients should fetch this first and use the returned `models`, `capabilities.audio_formats` and `capabilities.upload_method…
- [Sessions Overview](https://developer.eka.care/ekascribe/api-reference/sessions/overview.md): Session-based voice capture and transcription — the core EkaScribe flow
- [Create Session](https://developer.eka.care/ekascribe/api-reference/sessions/create-session.md): Create a new scribing session. Returns a `session_id` that must be used in every subsequent call (audio upload, end session, status polling) and an `upload_url` to which audio is sent. Only `upload_type` is required — use `single` (one audio file, max 10 MB via the API; for larger recordings use the…
- [Upload Audio](https://developer.eka.care/ekascribe/api-reference/sessions/upload-audio.md): Upload audio as a raw binary body. For `single` uploads (the default upload type), send one complete recording (max 10 MB) and the server performs Voice Activity Detection (VAD) chunking inline — for larger recordings use `chunked` uploads or the SDKs. For `chunked` uploads, call this repeatedly wit…
- [Stream Audio (WebSocket)](https://developer.eka.care/ekascribe/api-reference/sessions/stream-audio.md): Real-time audio streaming for upload_type: stream
- [End Session](https://developer.eka.care/ekascribe/api-reference/sessions/end-session.md): Finalize the session and start asynchronous processing. After this call no further audio uploads are accepted. The server collects and orders all uploaded chunks, commits the session, and queues it for transcription and template extraction. Poll `GET /voice/v1/sessions/{session_id}` (or use a webhoo…
- [Get Session](https://developer.eka.care/ekascribe/api-reference/sessions/get-session.md): Retrieve the current status of a session and, once processing finishes, its transcript and structured template results. The **HTTP status code** signals progress: `202` still processing, `200` completed, `206` completed with partial results, `410` expired, `404` not found. After calling End Session,…
- [Get Sessions](https://developer.eka.care/ekascribe/api-reference/sessions/get-sessions.md): List past sessions for the authenticated user, newest first. Cancelled and archived sessions are excluded. Pass `count` to cap the number of sessions returned. Pass `oid` to fetch sessions of a specific patient instead (up to 10 by default — override with `count`).
- [Get Session Audio](https://developer.eka.care/ekascribe/api-reference/sessions/get-audio.md): Fetch the complete recording of a session as a presigned download URL (single combined MP3). Available for businesses with full-audio access enabled — contact support to enable it for your workspace. The combined audio is prepared in the background after End Session; until it is ready this endpoint…
- [Update Session](https://developer.eka.care/ekascribe/api-reference/sessions/update-session.md): Update a session's metadata before it is committed. Use this to attach or correct `patient_details`, change the requested `templates`, adjust `language_hint`, or switch `session_mode` / `model`. `session_mode` and `model` can only be changed while the session is still open (before End Session) — att…
- [Process Template](https://developer.eka.care/ekascribe/api-reference/sessions/process-template.md): After a session ends, generate another document from it for the given template. Every template processed — via Create Session `templates` or this API — creates a document, listed in the session's documents. The call is asynchronous: it returns `202` with a new `document_id`; fetch it with Get Sessio…
- [Create Template](https://developer.eka.care/ekascribe/api-reference/templates/create-template.md): Create a custom note template. Describe the exact structure, sections and style you want in `desc` using plain text or markdown — for example "SOAP note with Subjective, Objective, Assessment, Plan; use bullet points; include a medication table". EkaScribe uses this description as the authoring inst…
- [List Templates](https://developer.eka.care/ekascribe/api-reference/templates/list-templates.md): List every template available to your workspace — Eka's default templates (e.g. `clinical_notes_template`, `transcript_template`) plus any custom templates you created. The full template object is returned for each entry, so this is also the read path for a single template: filter the response by `i…
- [Update Template](https://developer.eka.care/ekascribe/api-reference/templates/update-template.md): Update a custom template's title or description. Only the fields you send are changed. Default (Eka-provided) templates cannot be modified.
- [Delete Template](https://developer.eka.care/ekascribe/api-reference/templates/delete-template.md): Archive (soft-delete) a custom template. The template stops appearing in List Templates and can no longer be used for new sessions; notes already generated with it are unaffected.
- [Create or Update Document](https://developer.eka.care/ekascribe/api-reference/documents/create-update-document.md): Create a new document on a session (omit `document_id` → `201`), or update an existing one (include `document_id` → `200`) — for example to save a doctor's edits to generated notes. Every response includes a presigned **PUT** URL: upload the document content (markdown) to that URL to store it.
- [Get Document](https://developer.eka.care/ekascribe/api-reference/documents/get-document.md): Fetch a document's metadata and a presigned **GET** URL to download its content (markdown). Use this to retrieve generated notes by `document_id` — e.g. the `document_id` returned by Get Session or Process Template.
- [List Session Documents](https://developer.eka.care/ekascribe/api-reference/documents/list-session-documents.md): Fetch a session's full record — status, patient details, audio quality matrix and, most importantly, the list of **all documents** generated or created on the session (notes, transcripts, custom documents). Set `presigned=true` to include a download URL for each document.
- [Delete Document](https://developer.eka.care/ekascribe/api-reference/documents/delete-document.md): Archive (soft-delete) a document. The document disappears from session listings and Get Document returns `404` for it afterwards. Deleting an already-deleted document is a no-op and still returns success.
- [Eka FHIR Structure](https://developer.eka.care/ekascribe/resources/fhir-structure.md): FHIR resource mappings for Eka Care medical data
- [Complete FHIR Bundle Example](https://developer.eka.care/ekascribe/resources/fhir-bundle-example.md): Full JSON example of the Eka FHIR Bundle
- [System Requirements for Extension](https://developer.eka.care/ekascribe/resources/system-requirements.md)
- [IP Allowlisting for Clients](https://developer.eka.care/ekascribe/resources/ip-allowlisting.md): Allowlisting and endpoint information for Eka Scribe APIs & Audio transcription
- [Local Development with HTTPS (ngrok)](https://developer.eka.care/ekascribe/resources/local-development-ngrok.md): Give your local server a public HTTPS URL for testing with production APIs.
- [Overview](https://developer.eka.care/eka-medai/technologies/overview.md)
- [Lab report](https://developer.eka.care/eka-medai/technologies/lab-report.md)
- [Prescription](https://developer.eka.care/eka-medai/technologies/presription.md)
- [Personally Identifiable Information (PII) extraction](https://developer.eka.care/eka-medai/technologies/pii-extraction.md)
- [Document Classification](https://developer.eka.care/eka-medai/technologies/document-classification.md)
- [Health Insurance Policy](https://developer.eka.care/eka-medai/technologies/health-insurance.md)
- [Discharge summary](https://developer.eka.care/eka-medai/technologies/discharge-summary.md)
- [Medical Scribe](https://developer.eka.care/eka-medai/technologies/medical-scribe.md)
- [Medical snomed coder](https://developer.eka.care/eka-medai/technologies/medical-snomed-coder.md)
- [Medical summary](https://developer.eka.care/eka-medai/technologies/medical-summary.md)
- [Medical Entity Codification](https://developer.eka.care/eka-medai/technologies/codification/overview.md)
- [SNOMED CT](https://developer.eka.care/eka-medai/technologies/codification/snomed.md)
- [LOINC](https://developer.eka.care/eka-medai/technologies/codification/loinc.md)
- [Medication](https://developer.eka.care/eka-medai/technologies/codification/medication.md)
- [ICD-10-CM](https://developer.eka.care/eka-medai/technologies/codification/icd-10-cm.md)
- [Risk assessment](https://developer.eka.care/eka-medai/technologies/risk-assessment.md)
- [Symptom checker](https://developer.eka.care/eka-medai/technologies/symptom-checker.md)
- [Health bot](https://developer.eka.care/eka-medai/technologies/health-bot.md)
- [Indian Branded Drugs](https://developer.eka.care/eka-medai/indian_branded_drugs.md)
- [Indian Treatment Protocols](https://developer.eka.care/eka-medai/indian_treatment_protocols.md)
- [Spotlight](https://developer.eka.care/eka-medai/spotlight.md)
- [Datasets](https://developer.eka.care/eka-medai/datasets.md)
- [Models](https://developer.eka.care/eka-medai/models.md)
- [Overview](https://developer.eka.care/ai-tools/agent-kit/introduction.md): Build AI agents with Echo - an open-source, LLM-agnostic framework
- [Quickstart](https://developer.eka.care/ai-tools/agent-kit/quickstart.md): Build your first AI agent with Echo in 5 minutes
- [Installation](https://developer.eka.care/ai-tools/agent-kit/installation.md): Install Echo - open-source agent framework
- [Configuration](https://developer.eka.care/ai-tools/agent-kit/configuration.md): Configure LLMs, tools, and agent settings
- [Agents](https://developer.eka.care/ai-tools/agent-kit/agents.md): Build agents with GenericAgent
- [Tools](https://developer.eka.care/ai-tools/agent-kit/tools.md): Create base tools, elicitation tools, and use MCP tools
- [LLM Providers](https://developer.eka.care/ai-tools/agent-kit/llm-providers.md): Configure OpenAI, Anthropic, and Gemini
- [Streaming](https://developer.eka.care/ai-tools/agent-kit/streaming.md): Real-time response streaming with typed events
- [MCP Integration](https://developer.eka.care/ai-tools/agent-kit/mcp-integration.md): Connect to MCP servers for external tools
- [Examples](https://developer.eka.care/ai-tools/agent-kit/examples.md): Complete working examples
- [Overview](https://developer.eka.care/ai-tools/synapse/introduction.md): Add a Synapse AI medical assistant to any website, React app, or custom UI
- [Choose your integration](https://developer.eka.care/ai-tools/synapse/choose-integration.md): Decide between the embed widget, the React SDK, and the core SDK
- [Quickstart](https://developer.eka.care/ai-tools/synapse/embed/quickstart.md): Add the MedAssist widget to any website with one tag and a script
- [Customization & overrides](https://developer.eka.care/ai-tools/synapse/embed/customization.md): Every attribute, theme option, and config override for the embed widget
- [JavaScript API](https://developer.eka.care/ai-tools/synapse/embed/javascript-api.md): Configure the embed widget programmatically with EkaMedAssist.init()
- [Installation & setup](https://developer.eka.care/ai-tools/synapse/react/installation.md): Render the prebuilt MedAssist chat widget inside your React app
- [Configuration reference](https://developer.eka.care/ai-tools/synapse/react/configuration.md): Every option in MedAssistConfig
- [Theming & design system](https://developer.eka.care/ai-tools/synapse/react/theming.md): Brand the MedAssist widget with the Eka design system
- [Quickstart](https://developer.eka.care/ai-tools/synapse/core/quickstart.md): Build a custom MedAssist UI on the raw Synapse core SDK
- [Events](https://developer.eka.care/ai-tools/synapse/core/events.md): Subscribe to real-time events from the Synapse session
- [Tool calls & elicitation](https://developer.eka.care/ai-tools/synapse/core/tool-calls.md): Render the inputs the agent asks for and send results back
- [Voice & audio](https://developer.eka.care/ai-tools/synapse/core/voice.md): Record audio and run voice-mode conversations
- [API reference](https://developer.eka.care/ai-tools/synapse/core/api-reference.md): Methods, types, and enums of @eka-care/medassist-core
- [Eka EMR MCP Server](https://developer.eka.care/ai-tools/mcp-server/introduction.md): Give your AI assistant direct access to Eka.care — book appointments, manage patients, create prescriptions, and more.
- [Remote MCP](https://developer.eka.care/ai-tools/mcp-server/remote-mcp.md): Connect any AI client to Eka.care in minutes — no installation required.
- [Local MCP SDK](https://developer.eka.care/ai-tools/mcp-server/local-mcp.md): Self-host the Eka MCP server on your own machine using API credentials.
- [Supported Tools](https://developer.eka.care/ai-tools/mcp-server/supported-tools.md): Complete list of available MCP tools and their capabilities
- [Authentication](https://developer.eka.care/ai-tools/mcp-server/authentication.md): Securely connect your AI assistant to Eka.care
- [MedAI Tools MCP Server](https://developer.eka.care/ai-tools/medai-tools-mcp/introduction.md): Ground your AI assistant in verified Indian medical data — drug search, treatment protocols, pharmacology, and 403 clinical calculators.
- [Quickstart](https://developer.eka.care/ai-tools/medai-tools-mcp/quickstart.md): Connect your AI client to MedAI Tools in minutes using the hosted server.
- [Tool Reference](https://developer.eka.care/ai-tools/medai-tools-mcp/tools.md): Complete reference for all 6 MedAI Tools — parameters, return values, and usage examples.
- [Authentication](https://developer.eka.care/ai-tools/medai-tools-mcp/authentication.md): Configure authentication for MedAI Tools — open mode for development, EkaCare OAuth for production.
- [Health Quiz](https://developer.eka.care/cookbook/whats-possible/health-assessment.md): Building a full stack health quiz app with just 4 Function calls, using eka-care's web SDK
- [Medication Search](https://developer.eka.care/cookbook/whats-possible/medicine-lookup.md): Building a full stack Building a medication search app using the Eka Care SDK's medication search module.
- [Appointments Management](https://developer.eka.care/cookbook/whats-possible/appointment-management.md): Building an appointments management app using the Eka Care SDK's appointments module.
- [Patients Management App](https://developer.eka.care/cookbook/whats-possible/patient-management.md): Building a patients management app using the Eka Care SDK's patients module.
- [Changelog](https://developer.eka.care/changelog.md): Latest updates and improvements to the Eka Developer Platform.
- [EkaScribe Changelog](https://developer.eka.care/ekascribe-changelog.md): Updates and improvements to EkaScribe — transcription and clinical documentation.
- [EMR Changelog](https://developer.eka.care/emr-changelog.md): Updates and improvements to the Eka EMR platform — patient records, prescriptions, billing, and workflows.
- [EkaAgents Changelog](https://developer.eka.care/ekaagents-changelog.md): Updates and improvements to EkaAgents — MCP Server, Echo Agent Kit, MedAssist, and agent workflows.
- [Weekly Updates](https://developer.eka.care/weeklyupdates.md): Weekly summary of user-facing changes across the Eka platform.
- [Under the Hood](https://developer.eka.care/under-the-hood.md): Monthly transparency post covering infrastructure, reliability, performance, and security work across the Eka platform.
## OpenAPI Specs
- [openapi](https://developer.eka.care/ekascribe/api-reference/openapi.yaml)
- [post_webhook](https://developer.eka.care/api-reference/doc-tool/post_webhooks/post_webhook.yaml)
- [doc-tool](https://developer.eka.care/api-reference/doc-tool/doc-tool.yaml)
- [registration](https://developer.eka.care/api-reference/user-app/abdm-connect/registration.yml)
- [fetch-assessment-v2](https://developer.eka.care/api-reference/health-ai/assessment/fetch-assessment-v2.yml)
- [questionnaire_data](https://developer.eka.care/api-reference/health-ai/assessment/questionnaire_data.yml)
- [questionnaire-v2](https://developer.eka.care/api-reference/health-ai/assessment/questionnaire-v2.yml)
- [references](https://developer.eka.care/api-reference/knowledge-base/references.yaml)
- [med-link](https://developer.eka.care/api-reference/health-ai/medical-entity-codification/med-link.yaml)
- [patient_directory](https://developer.eka.care/api-reference/doc-tool/patient-directory-apis/patient_directory.yml)
- [ip-allowlisting-for-clients](https://developer.eka.care/api-reference/doc-tool/ip-allowlisting-for-clients.yaml)
- [records](https://developer.eka.care/api-reference/user-app/records/records.yaml)
- [authorization](https://developer.eka.care/api-reference/authorization/authorization.yml)
- [initialize-assessment](https://developer.eka.care/api-reference/health-ai/assessment/assessment-flow/initialization/initialize-assessment.yml)
- [ekascribe](https://developer.eka.care/api-reference/health-ai/ekascribe/ekascribe-v2/ekascribe.yaml)
- [medassist-apis](https://developer.eka.care/api-reference/health-ai/medassist/medassist-apis.yaml)
- [webhooks](https://developer.eka.care/api-reference/connect/webhooks/webhooks.yml)
- [vitals](https://developer.eka.care/api-reference/user-app/vitals/vitals.yaml)
- [refrences](https://developer.eka.care/api-reference/medical-db/refrences.yaml)
- [voice](https://developer.eka.care/api-reference/health-ai/ekascribe/voice.yaml)
- [audio-transcribe](https://developer.eka.care/api-reference/health-ai/ekascribe/audio-transcribe.yaml)
- [fetch-assessments-by-id](https://developer.eka.care/api-reference/health-ai/assessment/fetch-assessments-by-id.yml)
- [component](https://developer.eka.care/api-reference/health-ai/assessment/component-info/component.yml)
- [submit-assessment](https://developer.eka.care/api-reference/health-ai/assessment/assessment-flow/submit/submit-assessment.yml)
- [continue-assessment](https://developer.eka.care/api-reference/health-ai/assessment/assessment-flow/continue/continue-assessment.yml)
- [tool_openapi](https://developer.eka.care/api-reference/doc-tool/tool_openapi.json)
- [privacy](https://developer.eka.care/api-reference/user-app/privacy/privacy.yaml)
- [notification](https://developer.eka.care/api-reference/user-app/notifications/notification.yml)
- [payment-api](https://developer.eka.care/api-reference/doc-tool/payment-api/payment-api.yml)
- [notify](https://developer.eka.care/api-reference/doc-tool/notify/notify.yml)