API PUT /claimprocs/{ClaimProcNum} returns 400 "Object reference not set to an instance of an object"

[avdhutkotkar]

Request

PUT {OpenDentalApiUrl}/claimprocs/{ClaimProcNum}

{
"DedApplied": 0,
"status": "Received",
"InsPayAmt": 82,
"writeOff": 126
}

Response

400 Bad Request
"Cannot update the ClaimProc: Object reference not set to an instance of an object.."

The claim proc is on a primary claim and is currently Status NotReceived with no payment attached. WriteOff + InsPayAmt equals FeeBilled exactly.

We only see this error at one practice for all of the claim proc updates. The same payload format works against every other practice we integrate with, which suggests something specific to this office's database or API server rather than the request itself.

Note : Payment posting is blocked for this practice so eager to find the answer to this and get this resolved.

Questions

1. What are the possible causes of this error on this endpoint?
2. How can we determine which one applies here — is there an API-side log, or a query we can run against the office database to identify the data causing it?
3. What do we need to correct for this update to go through?
4. Could you please check the reason of having NRE and have a proper message in future for such data?

[justine]

Request

PUT {OpenDentalApiUrl}/claimprocs/{ClaimProcNum}

{
"DedApplied": 0,
"status": "Received",
"InsPayAmt": 82,
"writeOff": 126
}

Response

400 Bad Request
"Cannot update the ClaimProc: Object reference not set to an instance of an object.."

The claim proc is on a primary claim and is currently Status NotReceived with no payment attached. WriteOff + InsPayAmt equals FeeBilled exactly.

We only see this error at one practice for all of the claim proc updates. The same payload format works against every other practice we integrate with, which suggests something specific to this office's database or API server rather than the request itself.

Note : Payment posting is blocked for this practice so eager to find the answer to this and get this resolved.

Questions

1. What are the possible causes of this error on this endpoint?
2. How can we determine which one applies here — is there an API-side log, or a query we can run against the office database to identify the data causing it?
3. What do we need to correct for this update to go through?
4. Could you please check the reason of having NRE and have a proper message in future for such data?

Hello avdhutkotkar,

We spent several hours investigating this issue and were able to narrow the error down significantly. The API request itself does not appear to be the cause. The request is being handled normally until Open Dental encounters data in the office database that appears to be inconsistent with data normally created through Open Dental.

This may indicate that third-party software has modified the Open Dental database directly rather than using the API. If so, this can result in database relationships that Open Dental does not normally expect and may cause errors in both Open Dental and the API.

Since this appears to be specific to the office database and may involve other third-party software, please reach out to us directly via email so we can gather the necessary office specific details. This type of troubleshooting is better suited for email than the forum. You can find the API support email listed in the Developer Portal.

Thanks!

[avdhutkotkar]

Hello we have initiated email for this

Subject : Not able to Update ClaimProcedures : API PUT /claimprocs — 400 "Object reference not set to an instance of an object" (forum topic 8714)