Register an app
Create a developer account at developer.smileline.io, register an OAuth app, and understand the lifecycle from development to approval.
Third-party apps connect to Smileline over OAuth 2.0. You register the app once on the developer portal; practices then connect it themselves, in either region, and can see and revoke it from their own settings.
Create a developer account
Go to developer.smileline.io/sign-in and enter your email address. Smileline emails you a sign-in link; there is no password, and you do not need a Smileline practice. The same form creates the account on first use.
Register the app
Click New app and name it. Practices see this name on the consent screen and in Settings → Integrations → Connected apps.
Copy the client secret from the dialog. It is shown once. The client id is public and always visible; the secret can be regenerated later, which replaces it immediately in every region.
On Settings, add your redirect URIs (exact match; HTTPS, or plain HTTP on localhost only), a description, logo URL, website, privacy policy URL, terms URL and support email, and tick the permission areas the app needs.
On Webhooks, optionally give the app one delivery URL and choose events. See App webhooks.
Every save is published to both production regions. The Overview tab shows each region as Live, Publishing… or Retrying with the reason; a region that cannot be reached is retried until it catches up, and you never need to publish by hand.
Lifecycle
| Status | Meaning |
|---|---|
| In development | Live in both regions, marked unreviewed on the consent screen, at most 25 connected practices per region. |
| Awaiting review | You submitted it; the cap and the notice still apply while Smileline reviews it. |
| Approved | No connection cap and no notice. |
| Changes requested | Reviewed and not approved yet. The note from Smileline is on the Submit tab; the app keeps working under the cap while you address it. |
| Disabled | Smileline switched it off. Every token is refused at once and its webhook endpoints are archived. |
See Testing for what the cap means in practice and Approval for the review.
What the app can reach
An app acts as the practice member who authorised it, narrowed by the areas it was granted. It can never do more than that person's role allows, and it cannot reach the clinical record, account or billing surfaces. The Authentication page describes the token semantics that apply to every OAuth connection.