Skip to main content
PATCH
/
dr
/
v2
/
appointment
/
{appointment_id}
Update Appointment V2
curl --request PATCH \
  --url https://api.eka.care/dr/v2/appointment/{appointment_id} \
  --header 'Content-Type: application/json' \
  --header 'auth: <auth>' \
  --data '{
  "clinic_id": "6742984",
  "doctor_id": "6742984",
  "patient_id": "6742984",
  "appointment_details": {
    "start_time": 1730189586,
    "end_time": 1730189586,
    "mode": "VIDEO",
    "custom_attributes": {},
    "video_connect": {
      "vendor": "other",
      "url": "https://meet.google.com/landing"
    }
  },
  "partner_meta": {
    "key1": "value1"
  },
  "patient_details": {
    "dob": "1987-01-06",
    "designation": "Mr.",
    "first_name": "Test",
    "partner_patient_id": "6742984",
    "middle_name": "",
    "last_name": "Patient",
    "mobile": "+919999999999",
    "gender": "M",
    "address": {
      "city": "Bangalore",
      "pincode": 560049
    }
  },
  "display_meta": {}
}'
This response does not have an example.

Headers

​
auth
string
required
Example:

"auth"

Path Parameters

​
appointment_id
string
required

Query Parameters

​
partner_id
string

If set to 1 then appointment_id in path parameter should be partner_appointment_id else eka apppointment_id

Example:

"1"

Body

application/json
  • EkaIds
  • PartnerIds
​
clinic_id
string
required

Identifier for the clinic in Eka.

Example:

"6742984"

​
doctor_id
string
required

Identifier for the doctor in Eka.

Example:

"6742984"

​
patient_id
string
required

Identifier for the patient in Eka.

Example:

"6742984"

​
appointment_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. In case of update it will be completely overridden.

​
patient_details
object
  • DOB
  • AGE
​
display_meta
object
  • This field is a set of key-value pair.
  • The value corresponding to a key must be string, int, or float.
  • Keys in display_meta must not exceed 30 characters.
  • The value for a key must not exceed 50 characters.
  • These key-value pairs will be shown on the appointment card.
  • For key names, it is recommended to use underscores (_) instead of spaces. During display, underscores will be replaced with spaces, and the following letter will be capitalized automatically.
  • Example:
    "vendor_patient_id": "P41025551968206" will be shown as "Vendor Patient Id": "P41025551968206"

Response

OK