DEV Community

Cover image for How I made Dental APIs less painful than the dentist
CAmador
CAmador

Posted on

How I made Dental APIs less painful than the dentist

At the outset of my Dentrix integration I definitely felt like I was pulling teeth.

Welcome to this episode of SOAP/ XML nightmares, random auth failures and patient data that disappears. I'll be your host.

I thought Open Dental would be straightforward. It wasn't. SOAP/ XML everywhere, auth flows that worked once and broke and appointment slots overlapping. I don't want to reveal just HOW long I swam through null until I almost quit (this was my first). I tried Synchronizer, and it changed enough of this legacy horror story to share.

Appointments normalized, missing patient fields were flagged before they caused me anymore trouble, and Postman worked great.

I went from "why did I agree to this" to yeah this might work.

Hope this saves you time on your dental integration or saves time on your dental integration cavities. If not, lmk how it goes.

PRs welcome. Or sympathy.

[https://github.com/synchronizer-api/quickstart]

Top comments (1)

Collapse
 
shipfastdev profile image
Charles Weaver

This was such a great read and thanks for sharing! I’ve definitely felt the pain of dealing with dental APIs before, and your breakdown of the biggest headaches really hit home. Loved how you not only called out the problems but also showed practical ways to handle them.

The GitHub quickstart is a nice touch too. Wish I had that a couple years ago!