Has anyone else had issues with the API today? It's been down a few times today and wanted to see if it was an issue everyone else was having.
Thanks!
API Issues
-
- Posts: 5
- Joined: Fri Aug 14, 2015 8:11 am
Re: API Issues
eservices issues, chrome complaining about http 503 errors and SSL certificate expiry... Something's going on on OD's end.
-
- Posts: 107
- Joined: Wed Apr 06, 2022 12:04 pm
Re: API Issues
Called and confirmed... eServices are down which impacts the API service. They said to check again in an hour. What's frustrating is that although we run a local API on our hosted GCP server - we're still dependent on the eServices connector and Open Dental availability. Why? To make sure we're paying the $35 for an API key?
Can I suggest we remove OD server availability as a dependency for self-hosted solutions?
Can I suggest we remove OD server availability as a dependency for self-hosted solutions?
Re: API Issues
We apologize for the interruption of service from roughly 14:30 -20:30 PDT. Our internet provider experienced a severe outage in our region (cable cut) impacting Open Dental and thousands of others in our area. We have just come back online and the API is available.
The Local and Service Modes of the API use the internet (not the eConnector) to verify credentials with HQ. This is to verify the correct set of ApiPermissions for the customer key, that the customer key has not been disabled (either by the developer or the customer), and most importantly to ensure the registration key for the dental office matches the one assigned to the customer API key. In most cases, this validation takes less than a second and does not impact the Local or Service modes of the API. Additionally, these modes are protected from any issue impacting the eConnector/eServices as Local/Service webcalls to HQ do not require the eConnector to be running. This scale of internet/power outage at HQ is the only way the Local or Services modes can be impacted.
The Local and Service Modes of the API use the internet (not the eConnector) to verify credentials with HQ. This is to verify the correct set of ApiPermissions for the customer key, that the customer key has not been disabled (either by the developer or the customer), and most importantly to ensure the registration key for the dental office matches the one assigned to the customer API key. In most cases, this validation takes less than a second and does not impact the Local or Service modes of the API. Additionally, these modes are protected from any issue impacting the eConnector/eServices as Local/Service webcalls to HQ do not require the eConnector to be running. This scale of internet/power outage at HQ is the only way the Local or Services modes can be impacted.
-
- Posts: 107
- Joined: Wed Apr 06, 2022 12:04 pm
Re: API Issues
Appreciate the clarification, glad you're back up.