Hello,
We have been using the ClaimTrackings POST/PUT APIs, https://www.opendental.com/site/apiclaimtrackings.html but we have encountered an issue. When adding a new claim tracking status through the API, the username field shows as empty, creating inconsistencies for users. This is because there is no UserName field in the POST/PUT request body.
Interestingly, if we perform the same operation using Open Dental, the Claim Tracking Status appears correctly on the UI.
We kindly request an enhancement to the API to include the UserName field in the POST/PUT request body to resolve this inconsistency.
Please let me know if I can answer any additional questions about this request.
Thank you for your attention to this matter.
API Request: Addition of UserName Field in ClaimTrackings POST/PUT APIs
-
- Posts: 8
- Joined: Tue Nov 16, 2021 7:25 am
Re: API Request: Addition of UserName Field in ClaimTrackings POST/PUT APIs
Hello manish.bhalodi.tech9,manish.bhalodi.tech9 wrote: ↑Wed Mar 05, 2025 9:52 pmHello,
We have been using the ClaimTrackings POST/PUT APIs, https://www.opendental.com/site/apiclaimtrackings.html but we have encountered an issue. When adding a new claim tracking status through the API, the username field shows as empty, creating inconsistencies for users. This is because there is no UserName field in the POST/PUT request body.
Interestingly, if we perform the same operation using Open Dental, the Claim Tracking Status appears correctly on the UI.
We kindly request an enhancement to the API to include the UserName field in the POST/PUT request body to resolve this inconsistency.
Please let me know if I can answer any additional questions about this request.
Thank you for your attention to this matter.
The reason that field is intentionally omitted in Open Dental API is because the API made the claimtracking, not the user. In Open Dental, a user has to have permission to create/update a claimtracking. Simply supplying a valid usernum could circumvent office defined security permissions. However, I will add looking into this to our API development list.
Thanks!