Dolphin API

Dolphin Imaging and Management, the practice and imaging system for orthodontists and oral surgeons.

Hosting
On-premise
Versions
Group
Orthodontics
NodePythoncURL
// Trade your API key for a 1-hour token
const auth = await fetch(
  'https://nexhealth.info/authenticates',
  { method: 'POST',
    headers: { 'Nex-Api-Version': 'v3.0.0',
      Authorization: process.env.NEX_API_KEY } }
).then(r => r.json());

// Read patients from a {name} practice.
// Same call on every supported system.
const patients = await fetch(
  'https://nexhealth.info/patients?' +
  'subdomain=smile-dental&location_id=105',
  { headers: { 'Nex-Api-Version': 'v3.0.0',
    Authorization: `Bearer ${auth.data.token}` } }
).then(r => r.json());// Trade your API key for a token
const auth = await fetch(
  'https://nexhealth.info' +
  '/authenticates',
  { method: 'POST',
    headers: {
      'Nex-Api-Version': 'v3.0.0',
      Authorization:
        process.env.NEX_API_KEY } }
).then(r => r.json());

// Patients from a {name} practice.
// Same call on every system.
const patients = await fetch(
  'https://nexhealth.info' +
  '/patients?' +
  new URLSearchParams({
    subdomain: 'smile-dental',
    location_id: 105 }),
  { headers: {
      'Nex-Api-Version': 'v3.0.0',
      Authorization:
        `Bearer ${auth.data.token}`
    } }
).then(r => r.json());import os, requests

# Trade your API key for a 1-hour token
auth = requests.post("https://nexhealth.info/authenticates",
    headers={"Nex-Api-Version": "v3.0.0",
             "Authorization": os.environ["NEX_API_KEY"]}).json()
token = auth["data"]["token"]

# Read patients from a {name} practice.
# Same call on every supported system.
patients = requests.get("https://nexhealth.info/patients",
    params={"subdomain": "smile-dental", "location_id": 105},
    headers={"Nex-Api-Version": "v3.0.0",
             "Authorization": "Bearer " + token}).json()import os, requests

# Trade your API key for a token
auth = requests.post(
  'https://nexhealth.info'
  '/authenticates',
  headers={
    'Nex-Api-Version': 'v3.0.0',
    'Authorization':
      os.environ['NEX_API_KEY']}
).json()
token = auth['data']['token']

# Patients from a {name} practice.
# Same call on every system.
patients = requests.get(
  'https://nexhealth.info'
  '/patients',
  params={
    'subdomain': 'smile-dental',
    'location_id': 105},
  headers={
    'Nex-Api-Version': 'v3.0.0',
    'Authorization':
      'Bearer ' + token}).json()# Trade your API key for a 1-hour token
curl -s -X POST "https://nexhealth.info/authenticates" \
  -H "Nex-Api-Version: v3.0.0" \
  -H "Authorization: $NEX_API_KEY"

# Read patients from a {name} practice.
# Same call on every supported system.
curl -s -G "https://nexhealth.info/patients" \
  -d subdomain=smile-dental -d location_id=105 \
  -H "Nex-Api-Version: v3.0.0" \
  -H "Authorization: Bearer $NEX_TOKEN"# Trade your API key for a token
API=https://nexhealth.info
curl -X POST $API/authenticates \
  -H "Nex-Api-Version: v3.0.0" \
  -H "Authorization: $NEX_API_KEY"

# Patients from a {name} practice.
# Same call on every system.
curl -G $API/patients \
  -d subdomain=smile-dental \
  -d location_id=105 \
  -H "Nex-Api-Version: v3.0.0" \
  -H "Authorization: Bearer $TOKEN"

What you can build on Dolphin

Every Synchronizer product works on Dolphin. These are the workflows developers ship on it most.

Booking and AI receptionists, intake forms, recall, payments, insurance verification, treatment plan follow-up.

Booking and AI receptionists

Intake forms

Recall

Payments

Insurance verification

Treatment plan follow-up

How Synchronizer connects to Dolphin

Dolphin runs on the practice’s own server, so Synchronizer installs there. Reads every few minutes, writes usually in seconds.

Synchronizer service
On-premise
Practice system
Dolphin
InstalledSelf-installer, 18 min
ReadsEvery few minutes
WritesUsually within seconds
Last read10:42:11 AM
StatusActive
Running on the practice’s server

Server-based systems

A small Windows service installed on the practice’s server with a product key from your portal. It reads the database and syncs changes to NexHealth, and runs your writes against the system.

Install guide
Cloud connector
Cloud
Practice system
Dolphin
SetupPractice login and extension
ReadsScheduled
WritesAppointments and patients
Last read10:41:48 AM
StatusActive
Running in the practice’s browser

Cloud systems

A browser extension or cloud connector, set up with a login the practice creates. Nothing to install on a server.

Setup guide

About Dolphin

Who makes it, who runs it, and what Synchronizer gives you on it.

Dolphin Imaging and Management is the practice and imaging system many orthodontists and oral surgeons run their offices on. It runs on a server inside the practice, with multi-clinic setups for groups that share one database. One connection covers every clinic in a multi-clinic setup.

On Dolphin, Synchronizer gives your app the whole practice through one API: patients, providers, the schedule and its open slots, recalls, insurance, documents and the ledger. Read it, and write back to it. Book, reschedule, cancel, confirm and check in appointments on the practice’s own schedule, create patients, post payments and adjustments to the ledger, file forms and documents to the chart, add insurance coverage, and log every call, text and email. A webhook confirms each write when it lands. The same endpoints work on all 15+ systems, so what you build for Dolphin runs everywhere. See the API reference.

Developers ship the full range on Dolphin: AI receptionists and online scheduling that book into the real calendar, intake forms whose answers land in the chart, recall and treatment plan follow-up from live data, insurance verification before the visit, and payments that post to the ledger so the books balance on their own. Orthodontic and oral surgery offices book the next visit before the patient leaves the chair, and a product that reads the real schedule makes that one tap instead of a call.

Connecting a Dolphin practice is a short install on the practice’s server that NexHealth handles with the office. Your app sends one onboarding link and gets a status for every step. Your sandbox is free and runs a real Open Dental practice, so you can build and test the full flow before your first live practice.

An AI agent that cannot read a live schedule and write a confirmed booking back into the health record system is just an answering machine.

Zachary Costa

Software developer, Yobi

Start building for free

One integration, 15+ systems. Build on live data from day one.