Skip to main content
POST
/
v1
/
scheduling
/
appointments
/
{id}
/
confirm
Confirmar una cita
curl --request POST \
  --url https://api.keebai.com/v1/scheduling/appointments/{id}/confirm \
  --header 'Authorization: Bearer <token>'
Moves the appointment from pending to confirmed. The call reads the current appointment first and rejects with 409 if the state isn’t pending (you can’t confirm an appointment that’s already confirmed, completed, or cancelled).

​
Endpoint

POST https://api.keebai.com/v1/scheduling/appointments/:id/confirm

​
Required scope

scheduling:appointments:confirm

​
Path params

ParamTypeDescription
idstringAppointment id.

​
Headers

HeaderRequiredValue
AuthorizationYesBearer kbai_pk_<token>
No body required.

​
Example request

curl -X POST https://api.keebai.com/v1/scheduling/appointments/9d5b1f4e-7c2a-4a4d-9d3e-9f1b1f8c7a3a/confirm \
  -H "Authorization: Bearer kbai_pk_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"

​
Response

​
200 OK

Returns the appointment with status: "confirmed". Shape identical to the body of GET /appointments/:id.

​
409 Conflict

{
  "error": {
    "code": "INVALID_APPOINTMENT_STATE",
    "message": "Sólo se puede confirmar una cita en estado 'pending' (estado actual: 'confirmed')."
  }
}

​
404 Not Found

The appointment doesn’t exist or belongs to another company.

​
401 Unauthorized · 403 Forbidden

Same semantics as the rest of the public API.

Authorizations

​
Authorization
string
header
required

Personal Access Token con prefijo kbai_pk_. Generar desde el portal con permiso developer.manage_tokens.

Path Parameters

​
id
string
required

Response

200

Cita confirmada