Subscription issue

[PBECKER]

Hello

We are trying to implement

The data we pass for post request is below :

{
"EndPointUrl": "https://dev.meetaxle.com/OpenDentalPatientUpdate.aspx/",
"Workstation": "AXLE-DEV",
"WatchTable": "Patient",
"PollingSeconds": 5,
"DateTimeStart": "2023-01-01"
}

or

{
"EndPointUrl": "https://dev.meetaxle.com/OpenDentalPatientUpdate.aspx/",
"Workstation": "AXLE-DEV",
"WatchTable": "Appointment",
"PollingSeconds": 5,
"DateTimeStart": "2023-01-01"
}

After creating above Subscription we are not receiving any callback to our Endpointurl on patient or appointment update.

Can you please provide us with any tips on what we may be doing incorrectly?

Thank you Open Dental API Team

[SLeon]

Good morning,

Just yesterday I posted an API Guide covering Subscriptions and Events here that you might find helpful. Have you already checked for the issues mentioned in the Troubleshooting section?

[PBECKER]

Hello Sarah

Yes we loved the new subscription and events document that was just posted a couple days ago.

We have successfully subscribed to "Patients" with no issues

When any change is made in the patient demographics for example patient name, date of birth, gender, phone number so we're not receiving the call back. greatly appreciate any pointers.

Thanks a ton Sarah!

-Pedro

[SLeon]

Good morning Pedro,

I am glad you enjoyed the latest API guide and am sorry you are still experiencing issues. Which troubleshooting steps have you tried? The first two bullet points from the guide resolve this for most customers.

• Ensure an instance of Open Dental (or the API Service) is running to process the subscription.
• Ensure the workstation of the subscription either 1) matches the machine running Open Dental/API Service, or 2) is blank. Events will not fire if there is a mismatch.
• For Database events, use Subscriptions GET a few times to see that the DateTimeStart is incremented by PollingSeconds. This will not occur if there is an issue processing the subscription due to the above reasons.
• For database events, make sure the action you are performing actually changes the database. Updating an Appointment’s Confirmed status from “Unconfirmed” to “Unconfirmed” does not actually change the data in the appointment table, and an event will not fire.
• Similarly, selecting the same patient repeatedly will not fire the PatientSelected UiEvent.
• Ensure the EndPointUrl of your Subscription is accurate. Check the documentation of your webhook service for required formatting. Support for some characters (such as trailing ‘/’) varies widely.

What results do you get when trying the third bullet point?