---
title: "Confirm appointment"
method: POST
path: "/v1/appointments/confirm"
tags: ["appointments"]
---

# Confirm appointment

`POST /v1/appointments/confirm`

## Request

- Base URL: `https://api-developer-sandbox.zocdoc.com`
- URL: `https://api-developer-sandbox.zocdoc.com/v1/appointments/confirm`
- Auth: one of:
  - OAuth 2
    - Client credentials
    - Token URL: `https://auth.zocdoc.com/oauth/token` scopes: `external.appointment.write`
  - OAuth 2
    - Authorization code: `https://auth.zocdoc.com/authorize`
    - Token URL: `https://auth.zocdoc.com/oauth/token` scopes: `external.appointment.write`

This endpoint is used to confirm an appointment in pending booking status. Developers must send a valid `appointment_id` as input in the request body.

## Request body

- ConfirmAppointmentRequestBody
  - `appointment_id` string, required

## Response `200`

Success

- AppointmentBaseResponse
  - `request_id` string, required: Unique request identifier for tracing
  - `data` AppointmentBaseResponseData, required: Data that will be returned upon a sucessful booking request
    - `appointment_id` string, required: The Zocdoc ID of the appointment.
    - `appointment_status` 'pending_booking' | 'confirmed' | 'booking_failed' | 'cancelled' | 'no_show' | 'pending_reschedule' | 'rescheduled' | 'reschedule_failed', required: The status of the appointment. See [Appointment Status definitions](/guides/glossary).
    - `developer_patient_id` string: The patient identifier provided by 3P developer. Null if not provided.

## Other responses

- `400`: Bad request.
- `401`: Unauthorized
- `403`: Forbidden
- `404`: Not found
- `409`: Conflict

---

[API](https://skmtc.dev/zocdoc/apis/zocdoc-bundle-api.md) - [All operations](https://skmtc.dev/zocdoc/apis/zocdoc-bundle-api/llms.txt) - [OpenAPI document](https://skmtc.dev/zocdoc/apis/zocdoc-bundle-api/revisions/965a6ca4ed12?raw)