Smileline
Sign in

Getting started

From an empty account to an app a practice can connect, in six steps. Each step links to the full reference.

  1. 01

    Create a developer account

    Sign in with your email address. There is no password: each sign-in sends a link to your inbox. You do not need a Smileline practice.

    Sign in →
  2. 02

    Create an app and keep its secret

    Name your app. The client id is public; the client secret is shown once, so store it in your secret manager before you close the dialog. You can regenerate it later, which replaces it immediately.

    Registering an app →
  3. 03

    Set redirect URIs and scopes

    Add the exact HTTPS redirect URIs your app uses (plain HTTP is allowed on localhost only) and tick the areas of practice data it needs, read or write. Practices see exactly that list when they connect.

    Scopes →
  4. 04

    Connect a practice

    Send a practice owner or manager to https://developer.smileline.io/oauth/authorize with your client id, PKCE challenge and redirect URI. They pick their region, review the scopes and approve. Exchange the code at https://developer.smileline.io/oauth/token and keep the api_base_url and organization_id from the response: every later request goes to that base URL.

    OAuth 2.0 →
  5. 05

    Receive webhooks

    Give your app one delivery URL and choose the events. Within about five minutes of a practice connecting, Smileline sends a challenge your endpoint must echo; from then on that practice's events arrive signed at your URL.

    App webhooks →
  6. 06

    Submit for approval

    Your app works in both regions from the start, capped at twenty-five connected practices per region and marked as unreviewed on the consent screen. Submit it when it is ready; approval removes the cap and the notice.

    Approval →
Create your first app