Documentation

cURL

curl --request PATCH \
  --url https://api.eka.care/abdm/v1/hiu/keyset \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "nonce": "<string>",
  "public_key": "<string>"
}
'

{
  "code": 123,
  "error": "<string>",
  "source_error": {
    "code": "<string>",
    "message": "<string>"
  }
}

Data

Update public keyset

API to update the HIU’s public keyset.

The client must generate a key pair, store the private key securely on their side, and push the public key and nonce to Eka using this API. This keyset can be updated at any time.

When requesting health data from external HIPs via ABDM, Eka shares this public key and nonce with the HIP. The client can then use their stored private key along with the public key shared by the external HIP to decrypt the health data received on the Data Push Webhook.

For details on key generation, encryption, and decryption, refer to the ABDM Encryption and Decryption Guide.

PATCH

abdm

hiu

keyset

cURL

curl --request PATCH \
  --url https://api.eka.care/abdm/v1/hiu/keyset \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "nonce": "<string>",
  "public_key": "<string>"
}
'

{
  "code": 123,
  "error": "<string>",
  "source_error": {
    "code": "<string>",
    "message": "<string>"
  }
}

Authorizations

Authorization

string

header

required

The API requires a Bearer token (JWT) for authentication.

Body

application/json

nonce

string

required

Base64-encoded nonce for encryption key derivation

public_key

string

required

Base64-encoded ECDH public key for encryption

Response

Overview Push care context data to HIU

⌘I

Authorization

End-to-End Encryption

Connect

HealthAI

Medical Database

General Tools

Doctor Tool

ABDM Connect

Medical Knowledge-bases

Medical Records

User App

Update public keyset

Authorizations

Body

Response