EOBAttaches POST/ SFTP Upload

For requests or help with our API
Post Reply
aearl23
Posts: 18
Joined: Wed Jan 22, 2025 3:33 pm

EOBAttaches POST/ SFTP Upload

Post by aearl23 » Thu Feb 20, 2025 7:23 pm

Is there a way where an sftp upload can be sent as a batch process to upload the same file for multiple patients?

justine
Posts: 284
Joined: Tue Dec 28, 2021 7:59 am

Re: EOBAttaches POST/ SFTP Upload

Post by justine » Fri Feb 21, 2025 9:21 am

aearl23 wrote:
Thu Feb 20, 2025 7:23 pm
Is there a way where an sftp upload can be sent as a batch process to upload the same file for multiple patients?
Hello aearl23,

The EobAttaches POST UploadSftp endpoint is only for claim payment EOB attachments, not for general patient file uploads. If you're trying to upload documents for multiple patients, the correct endpoint is POST /documents/UploadSftp, which allows uploads based on PatNum.

You’ll need to call it separately for each patient, as Open Dental does not currently support bulk document uploads in a single API call.

Thanks!

aearl23
Posts: 18
Joined: Wed Jan 22, 2025 3:33 pm

Re: EOBAttaches POST/ SFTP Upload

Post by aearl23 » Mon Mar 03, 2025 1:22 pm

We are trying to use the ClaimPaymentNum from a batch claim payment to perform a SFTP POST UPLOAD operation to the batch claim. We want to run a batch claim process and attach an eob to the claim so that all the patients on the claim have an attached EOB. While doing so, I got this error: OpenDental API error: 400 - "Error. This is most likely a version issue. The version that the customer is using might be too old to support the API method used."

I noticed that the listed version is 24.3.7 but in my PMS, the most recent update I see is 24.3.57 2/28/25. How can I correct this version error?

RyanH
Posts: 24
Joined: Thu Dec 19, 2024 8:33 am

Re: EOBAttaches POST/ SFTP Upload

Post by RyanH » Mon Mar 03, 2025 3:57 pm

aearl23 wrote:
Mon Mar 03, 2025 1:22 pm
We are trying to use the ClaimPaymentNum from a batch claim payment to perform a SFTP POST UPLOAD operation to the batch claim. We want to run a batch claim process and attach an eob to the claim so that all the patients on the claim have an attached EOB. While doing so, I got this error: OpenDental API error: 400 - "Error. This is most likely a version issue. The version that the customer is using might be too old to support the API method used."

I noticed that the listed version is 24.3.7 but in my PMS, the most recent update I see is 24.3.57 2/28/25. How can I correct this version error?
Hello aearl23,

The EOBAttaches endpoint should still work in your version of OD, so the error is probably unrelated. Would you be willing to provide more information about the SftpAddress you are using in your request body?

aearl23
Posts: 18
Joined: Wed Jan 22, 2025 3:33 pm

Re: EOBAttaches POST/ SFTP Upload

Post by aearl23 » Mon Mar 03, 2025 4:47 pm

I am using the sftp address from an AWS sftp server. I have been using the Upload SFTP for single claims without a problem, but when I do so with a batch payment, I get the error

aearl23
Posts: 18
Joined: Wed Jan 22, 2025 3:33 pm

Re: EOBAttaches POST/ SFTP Upload

Post by aearl23 » Tue Mar 04, 2025 9:04 am

Here is the error: OpenDental API error: 400 - "Error. This is most likely a version issue. The version that the customer is using might be too old to support the API method used."

justine
Posts: 284
Joined: Tue Dec 28, 2021 7:59 am

Re: EOBAttaches POST/ SFTP Upload

Post by justine » Tue Mar 04, 2025 2:12 pm

aearl23 wrote:
Mon Mar 03, 2025 4:47 pm
I am using the sftp address from an AWS sftp server. I have been using the Upload SFTP for single claims without a problem, but when I do so with a batch payment, I get the error
aearl23 wrote:
Tue Mar 04, 2025 9:04 am
Here is the error: OpenDental API error: 400 - "Error. This is most likely a version issue. The version that the customer is using might be too old to support the API method used."
Hi aearl23,

We had the opportunity to review your issue and confirmed that the API request itself is functioning correctly when tested independently via cURL. This indicates that the issue lies within your application’s implementation rather than the Open Dental API.

As a reminder, at this time, Open Dental does not provide direct API support beyond what is available in our documentation and forum discussions. We recommend debugging your application’s request handling, verifying the data being sent, and ensuring it matches the successful cURL request.

If you have further API-related questions, please continue using the forum. However, please note that responses are community-driven and provided as time allows.

Thanks!

Post Reply