Skip to main content
Question

API access for custom monthly reporting

  • Sep 28, 2026 11:38 AM UTC
  • 2 replies
  • 66 views

Forum|alt.badge.img+8

I did email  dentallypartnerships@henryscheinone.com a month a go but I haven’t had any reply, so I thought I would ask here:


We are looking at creating a small internal monthly report to help us understand treatment plan activity.

We would like to report, by dentist:

• the number and value of treatment plans created each month;
• how many subsequently result in treatment being booked or started;
• how much of the proposed treatment is eventually completed; and
• the time between creating a plan and treatment beginning.

I can see that the v1 API documentation includes treatment_plans, treatment_plan_items and treatment_appointments, which appear to contain the information we need. The current NexGen documentation does not seem to include equivalent treatment-plan endpoints.

Could you please confirm:

1. Whether we can obtain practice-owned, read-only v1 API access for this purpose.
2. Whether the required treatment and practitioner/user read permissions can be provided.
3. Whether v1 will continue to be supported for custom reporting, or whether equivalent NexGen endpoints are planned.
4. Whether there is a sandbox with synthetic treatment-plan data that we could use during development.
5. Whether there are any costs, Practice Integration Program requirements or restrictions we should be aware of.

The proposed application would be for our practice’s own use, would not write anything back to Dentally, and its management reports would contain aggregate figures rather than patient names or contact details.

2 replies

Forum|alt.badge.img
  • Newcomer
  • Oct 21, 2026 10:18 PM UTC

On your third question, v1 looks like the only thing that exists for custom reporting at the moment. There is a thread here called "NexGen API access to practices" where Ysy Lees said in August that NexGen is being released in groups and does not have parity with v1 endpoints yet, and that nobody can be given NexGen access until the Practice Integration Platform launches. Worth a read, it is the clearest answer I have found anywhere.
On your fourth, there is a sandbox listed in the v1 documentation, at api.sandbox.dentally.co. Whether it has synthetic treatment plan data in it I do not know.
On your fifth, the only place I have found that distinguishes anything is their pricing page. Starter and Essentials list integrations as "Approved partners", Pro lists them as "Custom". That looks relevant to what you are asking.
Your first question is the one I cannot answer and I would like to know it too. Whether a practice can get its own read-only access without going through the partner programme is not documented anywhere I can find, including the developer docs, which have no authentication page at all.
None of that is official, it is just what I pieced together from their own pages, so treat it accordingly. I am on the supplier side rather than a practice, in case that colours any of it.


Forum|alt.badge.img
  • Newcomer
  • Oct 23, 2026 8:28 PM UTC

​@FranBo  the part of my answer about nobody being able to get NexGen access is out of date. Dentally's October round-up, dated the 16th, says Level 4 users in the UK and APAC can now generate their own NexGen API credentials from Settings, without needing a partner integration. That went out six days before I replied and I missed it.
There's also a NexGen API Practice FAQs article in the help centre now that wasn't there when I looked. It confirms the Settings route for your own use, and it answers your third question directly: "the existing v1 APIs will continue to operate as normal", with no retirement date given.
Your point about treatment plan endpoints probably still stands though. The same article says development continues "until outcome parity with the current v1 APIs is achieved", so parity isn't there yet. So, you can get NexGen credentials today, v1 may still be the one that actually has what you need, and Dentally have now said in writing that it keeps working.
What the article doesn't cover is your second, fourth or most of your fifth. Nothing on scoping read-only permissions, nothing on a sandbox, nothing on cost. Those are still for them to answer.
One thing if you were thinking of handing this to an outside developer. The FAQ says the credentials "should only be used once, and should not be shared with others", and to treat them like a password. In-house is fine. External, they ask them to go through the partner application instead.