Page 1 of 1

Create PreAuth claim not working

Posted: Sun Jul 13, 2025 10:28 pm
by shripati.ukirde
Dear Open Dental API Team,

I’m encountering an issue while attempting to create a preauth claim without service date. The API returns a Bad Request error with the following message: "DateService year must be between 1880 and 2100."
We use POST https://api.opendental.com/api/v1/claims endpoint

Code: Select all

{
"PatNum": 1233,
"procNums": [123],
"ClaimType": "PreAuth",
"InsSubNum":123,
"PatRelat":"Self",
"ProvTreat":1,
"ProvBill":1
}
https://www.opendental.com/site/apiclaims.html
Could you please check this and let us know if we are missing anything? Please let me know if any additional information is needed.
Thank you for your time and assistance.

Re: Create PreAuth claim not working

Posted: Mon Jul 14, 2025 8:24 am
by RyanH
shripati.ukirde wrote: Sun Jul 13, 2025 10:28 pm Dear Open Dental API Team,

I’m encountering an issue while attempting to create a preauth claim without service date. The API returns a Bad Request error with the following message: "DateService year must be between 1880 and 2100."
We use POST https://api.opendental.com/api/v1/claims endpoint

Code: Select all

{
"PatNum": 1233,
"procNums": [123],
"ClaimType": "PreAuth",
"InsSubNum":123,
"PatRelat":"Self",
"ProvTreat":1,
"ProvBill":1
}
https://www.opendental.com/site/apiclaims.html
Could you please check this and let us know if we are missing anything? Please let me know if any additional information is needed.
Thank you for your time and assistance.
Hello shripati.ukirde.

We are currently investigating and working on a fix for this issue. In the meantime, you can work around this problem by setting the ProcDate field on the provided procedurelogs to a valid date between this range, such as the value in the DateTP field (the date it was originally Treatment Planned).

Thanks!

Re: Create PreAuth claim not working

Posted: Tue Jul 15, 2025 6:31 am
by shripati.ukirde
Hello RyanH

Thank you for the updates.

Re: Create PreAuth claim not working

Posted: Wed Jul 16, 2025 9:33 am
by RyanH
The fix for this issue has been implemented and is currently available in versions 25.2.20 and 25.1.45.