Dentally API

Name: Dentally API API
Brand: Dentally API
Availability: InStock

★ Only Publicly Available SpecHealthcareAppointment SchedulingapiKey31 EndpointsREST

For Agents

Manage dental patients, appointments, invoices, NHS claims, and fees in Dentally with read and write access across 31 endpoints.

Quickstart

Get started with Dentally API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"book a dental appointment in dentally"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Dentally API API.

Create and update patient records via /v1/patients endpoints

Book, retrieve, update, and cancel appointments through /v1/appointments

Check appointment availability before scheduling via /v1/appointments/availability

Read and write fees, invoices, and invoice items for billing flows

GET STARTED

Start building with Dentally API API

Explore with Jentic

View OpenAPI Spec

Jentic publishes the only available OpenAPI specification for Dentally API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for Dentally API, keeping it validated and agent-ready. Dentally is cloud-based dental practice management software used by independent practices and groups, primarily across the UK and APAC. The API exposes 31 endpoints covering patients, appointments, fees, invoices, NHS claims, contracts, custom fields, payment plans, accounts, and acquisition sources. Sandbox and APAC base URLs are provided alongside production, enabling integrations that span dental groups, recall systems, and patient-engagement tools.

Use Cases

Patterns agents use Dentally API API for, with concrete tasks.

★ Online Patient Booking

Power an online booking widget by checking clinician availability through GET /v1/appointments/availability and creating the appointment with POST /v1/appointments. Patient records can be created or updated in the same flow via /v1/patients, so a new patient becomes a real Dentally record at the moment of booking.

Call GET /v1/appointments/availability for the clinician, then POST /v1/appointments with the chosen slot and patient id.

Recall and Reminder Engine

Drive a recall and reminder workflow by listing appointments and patients, then sending reminders through SMS or email channels outside Dentally. The patient and appointment endpoints provide the structured data such recall engines need without needing to scrape the Dentally UI.

Pull the next 7 days of appointments via GET /v1/appointments, join to /v1/patients, and queue reminders for each.

NHS Claim Reporting

Run reports on NHS claim activity by listing /v1/nhs_claims and pulling individual claims by id. UK practice managers and finance teams can build dashboards that track submission status and outstanding claims without exporting CSVs from the Dentally UI.

Call GET /v1/nhs_claims with a date filter and aggregate the response by claim status to power a finance dashboard.

Group-Wide Practice Reporting

For dental groups operating multiple practices on Dentally, the /v1/accounts and /v1/invoices endpoints provide the cross-practice data needed for revenue, billing, and acquisition reporting. Acquisition sources can be analysed via /v1/acquisition_sources to attribute new patients.

List /v1/invoices for each account and aggregate total billed by month and by practice.

AI Agent Integration via Jentic

An assistant for a front desk or dental group operations team can use Jentic to chain availability lookups, patient creation, and appointment booking in a single conversation. Jentic resolves the API key from the vault and exposes a typed schema for each Dentally operation, removing the need to read the API documentation while building an integration.

Use Jentic to search for 'book a dental appointment', load POST /v1/appointments, and execute it for the selected slot and patient.

Key Endpoints

31 endpoints — jentic publishes the only available openapi specification for dentally api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/v1/patients

List patient records

POST

/v1/patients

Create a patient

GET

/v1/appointments

List appointments

POST

/v1/appointments

Create an appointment

GET

/v1/appointments/availability

Check appointment availability

GET

/v1/invoices

List invoices

GET

/v1/nhs_claims

List NHS claims

GET

/v1/fees

List configured fees

GET

/v1/patients

List patient records

POST

/v1/patients

Create a patient

GET

/v1/appointments

List appointments

POST

/v1/appointments

Create an appointment

GET

/v1/appointments/availability

Check appointment availability

GET

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Dentally API keys are stored encrypted in the Jentic vault. Agents reference operations by name and Jentic injects the key header at execution time, so the secret never appears in prompts or logs.

Intent-based discovery

Agents search by intent (e.g. 'book a dental appointment') and Jentic returns the matching Dentally operation along with its full input schema, so the agent can fill parameters and execute without reading docs.

Time to first call

Direct Dentally integration: 2-3 days for auth, environment switching, and resource lifecycle. Through Jentic: under an hour to chain patient creation, availability lookup, and appointment booking.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

DrChrono API

EHR with strong scheduling and clinical features for US medical and dental practices.

Choose DrChrono when the practice is US-based and needs broader EHR features beyond dental practice management.

Alternative

athenahealth API

Enterprise EHR and revenue cycle management API for medical groups.

Choose athenahealth when the customer is a multi-specialty US medical group rather than a UK or APAC dental practice.

Complementary

Twilio Messaging API

SMS delivery for appointment reminders and recalls triggered from Dentally data.

Use Twilio alongside Dentally when patient appointment reminders need to go out via SMS.

Complementary

SendGrid Mail API

Transactional email delivery for booking confirmations and recall emails.

Use SendGrid alongside Dentally when confirmations or recalls go out via email rather than SMS.

FAQs

Specific to using Dentally API API through Jentic.

Why is there no official OpenAPI spec for Dentally API?

Dentally does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Dentally API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Dentally API use?

The Dentally API uses an API key passed in a header. Through Jentic, the key is stored encrypted in the vault and injected at execution time, so the secret never enters the agent's prompt or memory.

Can I book an appointment with the Dentally API?

Yes. POST /v1/appointments creates an appointment for a patient, and GET /v1/appointments/availability lets you check open slots before booking. PUT /v1/appointments/{id} updates an existing appointment and DELETE /v1/appointments/{id} cancels it.

Does the Dentally API support NHS claims?

Yes. GET /v1/nhs_claims lists NHS claim records and GET /v1/nhs_claims/{id} returns a specific claim, supporting UK practices that need programmatic visibility of their NHS submissions.

What base URL should I use for the Dentally sandbox?

The OpenAPI spec lists three servers: production at https://api.dentally.co, sandbox at https://api.sandbox.dentally.co, and APAC at https://api.apac.dentally.com. Pick the one matching your environment when you call any /v1 endpoint.

How do I create a patient and book an appointment through Jentic?

Run `pip install jentic`, search for 'create a dentally patient', execute POST /v1/patients, then search for 'book a dental appointment' and execute POST /v1/appointments. Jentic carries the API key across both calls so the agent never handles it.