Smileline Developers

Build for the practice's front desk.

Connect your product to Smileline, the AI-powered CRM for dental practices in the UK and the US.

Connect, call and listen.

Practices connect your app, it calls their data, and their events come to you signed.

  • OAuth 2.0

    Practices connect your app themselves, and refresh tokens rotate on every use.

    OAuth guide
  • REST API

    Patients, appointments, journeys, tasks, conversations and more, one scope per area.

    API reference
  • Webhooks

    One delivery URL per app; every practice's events arrive signed, retried and replayable.

    App webhooks
No code? Smileline is on Zapier

Live on day one.

Every app works in both regions from the start, for up to 25 practices per region until we review it.

What developers ask us first.

Do I need a Smileline practice to build an app?

No. Sign in with your email; there is no password and no practice needed. Your app can connect to real practices from the moment it exists: your own, a client's with their agreement, or a Smileline trial practice.

Is there a sandbox?

No separate one. Apps are live in both regions from the start. Until Smileline approves them, they are capped at 25 connected practices per region and marked unreviewed on the consent screen. Approval lifts the cap and the notice in both regions within minutes, and the same client id, secret, tokens and webhook endpoints keep working.

How do UK and US practices connect?

Through one authorise URL and one token URL. The owner or manager picks UK & Europe or United States, and the token response gives you the api_base_url for that practice's region. A code or token from one region means nothing to the other.

What can a connection do?

It acts as the practice member who authorised it, narrowed to the areas granted. It can never do more than that person's role allows, and it never reaches the clinical record, billing or account surfaces.

How long do tokens last?

Access tokens last one hour. With offline_access, refresh tokens last 30 days and rotate on every use, so store the replacement each time. PKCE (S256) is mandatory, and there is no client-credentials grant.

When do webhooks start?

Within about five minutes of a practice connecting, Smileline creates its endpoint and sends a challenge. Delivery starts after your first successful echo. Events in between are not queued, so backfill them from the list endpoints.

How are failed deliveries retried?

Network errors, timeouts and 408, 425, 429 or 5xx responses become eligible for another attempt after 1 minute, 5 minutes, 30 minutes, 2 hours, 8 hours and 24 hours. Every delivery is signed with X-SmileLine-Signature and can be replayed.

Tell us what you are building.

Not sure where it fits? Talk to us before you write a line of code.