---
title: "Update Appointment"
method: PATCH
path: "/dr/v1/appointment/{appointment_id}"
tags: ["Appointment API"]
---

# Update Appointment

`PATCH /dr/v1/appointment/{appointment_id}`

### Overview

This API endpoint is used to update an existing appointment.

## Path parameters

- `appointment_id` string, required

## Query parameters

- `partner_id` string

## Headers

- `auth` string, required

## Request body

- object
  - `custom_attributes` 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.
  - `start_time` integer — Start time of new appointment in epoch. To be used in order to reschedule appointment.
  - `end_time` integer — End time of new appointment in epoch. To be used in order to reschedule appointment.
  - `token` integer — A unique number given to each patient to indicate their position in the queue.
  - `video_connect` object
    - `vendor` string — Vendor identifier
    - `url` string — url for connecting online
    - `pt_joined` integer — Epoch time
  - `patient_details` union
    - object
      - `designation` 'Mr.' | 'Ms.' | 'Mrs.' | 'Miss.' | 'Kumar.' | 'Shri.' | 'Smt.' | 'Dr.' | 'Master.' | 'Baby.' | 'Mohd.' | 'B/O' — Title or designation of the patient
      - `first_name` string — First name of the patient
      - `partner_patient_id` string — Identifier for the partner’s patient.
      - `middle_name` string — Middle name of the patient (if any)
      - `last_name` string — Last name of the patient
      - `mobile` string — Mobile number of the patient, including country code
      - `gender` 'M' | 'F' | 'O' — Gender of the patient (e.g., 'M' for male, 'F' for female, 'O' for others)
      - `address` object — Address details of the patient
        - `city` string
        - `pincode` integer
      - `dob` string, date, required — Date of birth of the patient (YYYY-MM-DD)
    - object
      - `designation` 'Mr.' | 'Ms.' | 'Mrs.' | 'Miss.' | 'Kumar.' | 'Shri.' | 'Smt.' | 'Dr.' | 'Master.' | 'Baby.' | 'Mohd.' | 'B/O' — Title or designation of the patient
      - `first_name` string — First name of the patient
      - `partner_patient_id` string — Identifier for the partner’s patient.
      - `middle_name` string — Middle name of the patient (if any)
      - `last_name` string — Last name of the patient
      - `mobile` string — Mobile number of the patient, including country code
      - `gender` 'M' | 'F' | 'O' — Gender of the patient (e.g., 'M' for male, 'F' for female, 'O' for others)
      - `address` object — Address details of the patient
        - `city` string
        - `pincode` integer
      - `age` integer, required — Age in years
  - `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 `204`

OK

## Other responses

- `400` — Bad Request
- `404` — Not Found
- `500` — Internal Server Error

---

[API](https://skmtc.net/eka/apis/eka-developer-apis.md) · [All operations](https://skmtc.net/eka/apis/eka-developer-apis/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/eka/eka-developer-apis/revisions/9ea23456f722/schema)