Smileline
SettingsPmsSettingsPmsConnectionsIdBooking issuesIssueidResolve

Resolve a booking needing attention

A booking: retry, keep_local (complete it in Smileline only; never sent) or cancel — the last two only while the PMS cannot hold it (409 PMS_MAY_ALREADY_HAVE_IT). A move: retry (only while the visit still stands where the move found it and no newer move is live), dismiss (the visit stays as it is) or cancel (the booking is cancelled the normal way and the PMS cancel queued). A change not sent: retry or dismiss. `expectedGeneration` is the row's as listed; a row that changed since answers 409.

Loading the API reference…

List bookings needing attention GET

Bookings and moves Smileline parked for a person on this connection (newest first), then the confirmations and cancellations it couldn't send, each with its visit, patient, a plain reason code and the actions safe now. `patientId` lists that patient's only (Today and the patient page fix a parked booking there: save the patient's missing details with PATCH /patients/:id, then retry — the resend reads the record afresh). Cursor-paginated; a patient under erasure is never listed.

Activate a PMS connection with its credentials POST

Providers that take practice-supplied keys: CareStack (the practice's CareStack address on the US or UK domain and its account key, plus either the account id for the documented header sign-in or the practice's own vendor key, client id and client secret for the UK token sign-in), Open Dental (customer key, optional eConnector workstation), Dentally (a personal access token; refused with 422 PMS_CONNECTION_SCOPES_MISSING when it lacks a required permission) and Dentally NexGen (client id, client secret and practice id; 422 PMS_CONNECTION_PRACTICE_REFUSED when the credentials cannot reach that practice). Proves the credentials against the practice's own site list, seeds the site map from it and moves the connection to connecting, which starts the historical import; Open Dental and Dentally also register their live-update webhooks. CareStack and Dentally rotation is allowed only onto the same account; a different account is a disconnect. An organization may operate one PMS at a time, so activation is refused while another provider is live. A new Dentally or Dentally NexGen activation is refused with 409 PMS_EXPORT_IMPORTED once a Switch from Dentally import has written the practice's records; replacing the token of a running Dentally connection is not.