Skip to main content
Every Eka product uses the same keys and the same access token. Get them once, then build with any product: the scribe, records, agents, models or ABDM.

​
Get your API keys

1

Create a client in the console

Sign in to the Eka Care console and create a client. You get two values.

Client ID

Identifies your application to Eka’s APIs.

Client Secret

A confidential key, like a password, used with the client ID.
2

Building for doctors or patients?

Integrate Eka accounts with OpenID Connect (OIDC), or ask the healthcare provider for an API key from their workspace.
3

Set up your client

Send every request to https://api.eka.care. Any HTTP client works: Postman, cURL or the library for your language.
For keys or help, write to ekaconnect@eka.care.

​
Authenticate

1

Get an access token

Call client login with your client ID and client secret. You get an access token and a refresh token.
2

Send it with every request

Put the access token in the Authorization header of each API call.
3

Refresh it when it expires

The access token lasts about 30 minutes. A 401 Unauthorized means it has expired: call refresh token for a new one.
For server-to-server work that should not refresh every half hour, use a long-lived token.

​
Pick a product

Scribe

Turn a consultation into a structured note in your template.

Agents

Build an agent for your purpose and give it Eka’s medical tools.

Patient experiences

Booking sites, patient agents and the records the patient keeps.

Clinical intelligence

Read reports, code clinical terms and ground your AI in medical data.

ABDM

ABHA, linked records, consent, claims and the UHI network.

​
Connect your tools

Already run your clinic on Eka’s EMR? Connect it to the CRM or dashboard your team uses: appointments and visits from the EMR, admissions from IPD, and invoices and payments from Billing. Not sure where your product fits? Eka products lists every product, and the glossary explains the terms the docs use.