Postman Response - "The server has encountered an error."

For requests or help with our API
Post Reply
PBECKER
Posts: 125
Joined: Mon Jan 03, 2022 11:54 am

Postman Response - "The server has encountered an error."

Post by PBECKER » Tue Feb 15, 2022 12:19 pm

- All of a sudden we're having 2 practices that are returning "The server has encountered an error."

-We have also utilized postman and checked with a working api key compared to the two keys that don't work

Thus far we have verified the following:
-GET url is correct and operational for all other API keys
-our authorization info is correction and operational for all other practices
-We have validated the above utilizing postman
-We have also tried assigning new APIs keys and we're still presented with the "The server has encountered an error."

For the site practices that are returning "The server has encountered an error.", we have also verified the the API key is enabled on the dev site, in open dental and also in the econnector is operational and running with no issues

any ideas on what else would trigger the following "The server has encountered an error."

User avatar
jordansparks
Site Admin
Posts: 5739
Joined: Sun Jun 17, 2007 3:59 pm
Location: Salem, Oregon
Contact:

Re: Postman Response - "The server has encountered an error."

Post by jordansparks » Tue Feb 15, 2022 1:16 pm

We'll stop working on other things and focus on this problem. There should be no active bugs like this, so we'll work on it aggressively.
Jordan Sparks, DMD
http://www.opendental.com

User avatar
jordansparks
Site Admin
Posts: 5739
Joined: Sun Jun 17, 2007 3:59 pm
Location: Salem, Oregon
Contact:

Re: Postman Response - "The server has encountered an error."

Post by jordansparks » Tue Feb 15, 2022 1:25 pm

We're reaching out to you by email. We need to know which offices.
Jordan Sparks, DMD
http://www.opendental.com

SLeon
Posts: 476
Joined: Mon Mar 01, 2021 10:00 am

Re: Postman Response - "The server has encountered an error."

Post by SLeon » Tue Feb 15, 2022 2:21 pm

We have reached out to the developer and determined that the two dental offices in question had eConnectors on an older version not supported by Open Dental's API, which is only available in version 21.1 and later.

We are going to improve our error messages to better reflect the specific issue that was encountered in the failed request.

Post Reply