POST
/
dr
/
v1
/
appointment
curl --request POST \
  --url https://api.eka.care/dr/v1/appointment \
  --header 'Content-Type: application/json' \
  --header 'auth: <auth>' \
  --data '{
  "partner_appointment_id": "098765434567890",
  "partner_clinic_id": "642783",
  "partner_doctor_id": "8423994",
  "partner_patient_id": "6742984",
  "appointment_details": {
    "start_time": 1730189586,
    "end_time": 1730189586,
    "mode": "INCLINIC",
    "custom_attributes": {
      "label": [
        "vitals_submitted"
      ],
      "tags": [
        "paid",
        "in_consult"
      ]
    },
    "video_connect": {
      "vendor": "100ms",
      "url": "https://xyz.com",
      "conf": {
        "room_id": "r1",
        "room_sid": "rs1"
      }
    }
  },
  "patient_details": {
    "first_name": "Test",
    "mobile": "+919999999999",
    "gender": "M",
    "dob": "1987-01-16"
  },
  "partner_meta": {
    "encounter_id": "123"
  }
}'
{
  "appointment_id": "{{appointment_id}}"
}

Headers

​
auth
string
required

Body

application/json

The request body should contain either partner-specific fields or non-partner-specific fields for clinic and doctor identification.

​
partner_clinic_id
string
required

Identifier for the partner’s clinic. Please ensure the clinic is registered on the hub

​
partner_doctor_id
string
required

Identifier for the partner’s doctor. Please ensure the doctor is registered on the hub

​
partner_patient_id
string
required

Identifier for the partner’s patient. Please ensure the patient is registered beforehand using the "Add Patient" API.

​
appointment_details
object
required
​
partner_appointment_id
string
​
patient_details
object
​
partner_meta
object

This field is a set of key-value pair very specific to our partner and not visible in appointment queue. These key-value pairs are just stored at our end and echoed back in appointment related apis. We dont use it for any computation.

Response

201
application/json
OK
​
appointment_id
string
Get Appointment SlotsGet Appointment Details