POST
/
voice
/
api
/
v2
/
transaction
/
init
/
{session_id}
Initialize Transaction
curl --request POST \
  --url https://api.eka.care/voice/api/v2/transaction/init/{session_id} \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '{
  "additional_data": {
    "doctor": {
      "_id": "174097180967921",
      "profile": {
        "personal": {
          "name": {
            "f": "Divyesh",
            "l": ""
          }
        }
      }
    },
    "patient": {},
    "visitid": "09e4f00f-d665-4212-b77c-b2dd5f22bd92_1742560488782"
  },
  "mode": "dictation",
  "input_language": [
    "en-IN"
  ],
  "speciality": "general_medicine",
  "output_format_template": [
    {
      "template_id": "eka_emr_template",
      "language_output": "en-IN",
      "codification_needed": false
    }
  ],
  "transfer": "non-vaded",
  "batch_s3_url": "s3://m-pp-voice2rx/250307/R-S3-195D5131-D014-56A8-ACCF-2F8F2D230DEC/"
}'
{
  "status": "success",
  "message": "Transaction initialized successfully",
  "txn_id": "test_1234",
  "b_id": "b-1234567890"
}

​
Available Template IDs

Eka Care supports multiple output templates for different medical documentation needs. Choose the appropriate template ID based on your requirements:
Template IDDescriptionUse Case
clinical_notes_templateComprehensive clinical notes with structured medical informationGeneral clinical documentation, patient consultations
eka_emr_templateEMR-compatible format for electronic medical recordsIntegration with EMR systems
transcript_templateBasic transcription with minimal structuringSimple audio-to-text conversion

​
Supported Input Languages

Eka Care supports transcription in multiple languages. Specify the appropriate language ID in the input_language parameter:
Language IDLanguage Name
en-INEnglish (India)
en-USEnglish (United States)
hiHindi
guGujarati
knKannada
mlMalayalam
taTamil
teTelugu
bnBengali
mrMarathi
paPunjabi

Authorizations

​
Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Path Parameters

​
session_id
string
required

Unique identifier for the transaction session

Example:

"test_1234"

Body

application/json

Response

201
application/json

Transaction initialized successfully

The response is of type object.