Skip to main content
GrowDental runs voice-AI phone agents for dental practices: they answer inbound calls, place outbound calls, book and confirm appointments, and classify every conversation’s outcome. The Partner API lets platforms and practice-management systems plug into that calling engine for the practices you share with us.

​
What you can build

Read call results

Pull outcomes, durations, and summaries for every call at your granted practices — and transcripts and recordings once a BAA is in place.

Trigger calls

Queue outbound voice-AI calls to one or many contacts with a single POST. The platform handles dialing windows, retries, and concurrency.

Receive events

Register webhook endpoints and get signed, PHI-minimal notifications when calls complete, recordings become available, and call requests finish.

Feed patient data (coming soon)

Phase 2 adds batch intake of patients, appointments, and treatments to power recall and follow-up calling from your data. The draft schemas are already published in the API Reference so you can start mapping.

​
Access is invite-only

There is no self-serve signup. Because the API touches protected health information and outbound dialing, every partner is onboarded by our team:
  1. Contact us at partners@growdental.ai with what you’re building and which practices you work with.
  2. We create your partner app, grant it the relevant practices, and issue an API key scoped to what you need. The key is shown once — store it in a secret manager.
  3. For anything involving PHI (transcripts, recordings, patient intake), we execute a Business Associate Agreement first. PHI scopes are disabled in code until the BAA is on file.
Early access: the API surface documented here is v1 (Phase 1). The published OpenAPI spec is the contract of record — if the live API disagrees with these docs, tell us and we’ll fix the discrepancy.

​
Base URL

https://voice.growdental.ai/api/partner/v1
All endpoints are versioned in the path from day one. Requests are authenticated with your API key as a Bearer token — see Authentication.

​
Where to go next

Core concepts

Partners, keys, grants, calls, call requests, and webhooks — the five ideas the whole API is built on.

Authentication

Key format, scopes, rotation, and the BAA gate.

Receiving call outcomes

Set up a webhook endpoint and verify signatures, with working code.

API Reference

Every endpoint, generated from the OpenAPI spec.