---
title: "Record account-verified outcome of an uncertain appointment"
method: POST
path: "/v1/calendars/{connection_id}/appointments/{appointment_id}/resolve"
---

# Record account-verified outcome of an uncertain appointment

`POST /v1/calendars/{connection_id}/appointments/{appointment_id}/resolve`

## Request

- Base URL: `https://api.skysay.ai`
- URL: `https://api.skysay.ai/v1/calendars/{connection_id}/appointments/{appointment_id}/resolve`
- Auth: none declared

agents:write; bound to the authenticated organization/project and connection. Only unconfirmed requests can change; submitting requests and active reconciliation reads are refused. Inspect the provider account first. No provider request or booking retry is performed; the resolution is audited. Retrying the identical resolution is idempotent.

## Path parameters

- `connection_id` string, required
- `appointment_id` string, required

## Request body

- object
  - `organization_id` string
  - `project_id` string, required
  - `provider_checked` true, required
  - `provider_id` string: Required for booked; omit for verified not-created.
  - `state` 'booked' | 'not_created', required

## Response `200`

Safe appointment state and booking_succeeded flag

## Other responses

- `400`: Account verification or booking identity missing
- `404`: Appointment or connection not in workspace/project
- `409`: Appointment is submitting, verification is in progress, or the appointment was already resolved differently

---

[API](https://skmtc.dev/skysay/apis/skysay-api.md) · [All operations](https://skmtc.dev/skysay/apis/skysay-api/llms.txt) · [OpenAPI document](https://skmtc.dev/skysay/apis/skysay-api/revisions/95b8c66f99aa?raw)