DentiMax Communicator API

Name: DentiMax Communicator API
Brand: DentiMax Communicator API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentHealthcareAppointment SchedulingapiKey3 EndpointsREST

For Agents

List and schedule DentiMax appointments and send outbound messages to patients from external apps and agents.

Install Jentic One Beta

Connect the DentiMax Communicator API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the DentiMax Communicator API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with DentiMax Communicator API.

List upcoming appointments via GET /appointments

Schedule a new appointment for a patient with POST /appointments

Send a direct message to a patient through POST /messages

GET STARTED

Start building with DentiMax Communicator API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI specification for DentiMax Communicator API, keeping it validated and agent-ready. DentiMax Communicator is the patient-communication layer attached to the DentiMax dental practice management suite, used by US dental practices for scheduling and outbound patient messaging. The API exposes three endpoints covering listing appointments, scheduling appointments, and sending messages directly to a patient. Authentication uses a header API key, and the surface is intentionally narrow to support reminder, confirmation, and booking flows.

Use Cases

Patterns agents use DentiMax Communicator API for, with concrete tasks.

★ Custom Booking Widget

Embed a custom booking widget on a practice website that calls POST /appointments to schedule directly into DentiMax. Practices retain control of branding and form fields while ensuring the booking lands in the same schedule the front desk works from.

Collect patient and slot details from the widget, then POST them to /appointments and confirm the response on screen.

Patient Reminder Workflow

Run a reminder workflow that pulls upcoming appointments via GET /appointments and sends a personalised reminder for each via POST /messages. This reduces no-shows for DentiMax practices that prefer in-system messaging over a third-party SMS gateway.

Pull tomorrow's appointments via GET /appointments, then call POST /messages for each patient with a reminder body.

Outbound Patient Messaging

Send ad-hoc messages to patients straight from a CRM or operations console via POST /messages, without the staff member needing to log in to the DentiMax UI. Useful for follow-up notes, recall outreach, and one-off operational messages.

Call POST /messages with the target patient id and message body, and surface the delivery result back to the operator.

AI Agent Integration via Jentic

A front-desk assistant agent can use Jentic to schedule a new appointment and send a confirmation message in one conversation. Jentic resolves the API key from the vault and chains the two calls so the agent does not handle credentials or read API docs to act.

Use Jentic to search for 'schedule a dentimax appointment', call POST /appointments, then call POST /messages with a confirmation body.

Key Endpoints

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

METHOD

PATH

DESCRIPTION

GET

/appointments

List appointments

POST

/appointments

Schedule a new appointment

POST

/messages

Send a message to a patient

GET

/appointments

List appointments

POST

/appointments

Schedule a new appointment

POST

/messages

Send a message to a patient

Why Jentic?

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

Credential isolation

Your DentiMax API key is stored once, encrypted, by your own Jentic One instance and injected into the request header at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'schedule a dental appointment' or 'message a patient', and Jentic returns the matching DentiMax operation with its input schema so the agent calls the right endpoint without reading the docs.

Time to first call

FAQs

Specific to using DentiMax Communicator API through Jentic.

Why is there no official OpenAPI spec for DentiMax Communicator API?

DentiMax does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call DentiMax Communicator API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

What authentication does the DentiMax Communicator API use?

The DentiMax Communicator API uses an API key passed in a request header. Through Jentic, the key is stored in the encrypted vault and injected at execution time, so it never enters the agent's prompt.

Can I schedule appointments with the DentiMax Communicator API?

Yes. POST /appointments creates a new appointment in the practice schedule. GET /appointments returns the existing list, suitable for confirming the booking landed in the right slot.

Can I send a message to a patient through the DentiMax Communicator API?

Yes. POST /messages sends an outbound message to a specified patient, useful for reminders, confirmations, and recall outreach. Pair it with GET /appointments to drive a full reminder workflow.

Does the DentiMax Communicator API expose patient records?

This OpenAPI spec covers appointments and messages only - there are no patient CRUD endpoints in the documented surface. Patient identifiers used in /appointments and /messages must come from the DentiMax practice management system.

How do I drive a reminder workflow through Jentic?

Run `pip install jentic`, search for 'list dentimax appointments', then loop over the response and call POST /messages per patient. Jentic handles the API key for both operations from the vault.

Can I limit what my agent is allowed to do with the DentiMax Communicator API?

Yes. Because you run Jentic One yourself, you decide which of the DentiMax operations your agent may call, so you can grant read-only access to GET /appointments while withholding POST /appointments and POST /messages. The appointment and message details travel in the request body rather than a scoped URL path, so scoping happens at the operation level: scheduling and patient messaging are available only if you choose to add those operations. Your API key is held by your own instance and injected at execution time, keeping it out of the agent's prompt.

DentiMax Communicator API

Connect the DentiMax Communicator API to your agent

Capabilities

Start building with DentiMax Communicator API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs