What is the endpoint for eligibility for Availity?
I have looked at the API guide Availity API Guide | API Developer Portal. I have tried all of their endpoints that I can find in the documentation but they all end in a 500 error.
Cheers!
This is defiantly something of interest to us as well.
Any update on this? Thanks!
@juggernautsei Here availity end point base url https://api.availity.com
Then you can use the different end point below is token one end point for availity https://api.availity.com/availity/v1/token
@juggernautsei I have did elibility check and claim status check usign availity
@Nilesh_Hake thank for the response. Would you mind sharing the eligibility? What I have found with WayStar eligibility is if data is missing from the patient’s chart there is no way to have the eligibility done. Is that the same with Availity?
@juggernautsei I have to check response it was implemented long back with my client. I do not have the real data to send you eligibility response.
@juggernautsei If you card details we can test together response of eligibility request.
@Nilesh_Hake do you remember how you got your API access request approved for Availity APIs?
I’ve followed Availity API Guide | API Developer Portal & https://www.availity.com/documents/edi%20guide/edi_guide.pdf, and created an app in https://developer.availity.com and proven I can get access to the demo APIs that I can hit with manual curl requests. But I requested access to the “prod” APIs (Eligibility and Benefit Value Adds & Healthcare HIPAA Transactions) over 20 days ago but they both still say “(Pending Approval)”.
I’ve also submitted tickets using https://developer.availity.com/partner/support and I haven’t gotten a response.
The documentation also makes reference to a “Trading Partner” a few times but I have yet to find a way to identify or contact this person.
Do you remember how you got in contact with your Availity “Trading Partner” or if there was something else you had to do to get access to the “prod” Availity APIs?
Thanks!
@Goddard There response is very slow
1 Like
Sherwin - please check your email, I ask them for the documentation and they sent pdf and several links including QUA Credentials for RTE. If this is not what you want plz let me know.
Sure will, I saw something today. I will read over it. As far as I know, eligibility works. Am I barking up the wrong tree? @sjpadgett
Any info on how to setup availity API with openemr is very appropriate
In the practice settings, select x12 partners.
Add a new partner. You can add any endpoint you want. But I can tell you they will need some work to become fully functional. The system does not contain the infrastructure to handle any Eligibility endpoint. However, the system is equipped to process any X12 file to send via the claim tracker.
2 Likes
At the risk of derailing / going off topic / misunderstanding (I am very much not offended if someone hops in to correct me or offer better explanation), in my case, the path that lead me to the point of commenting in this thread last year (when I was first starting out) turned out to be a bit of a red herring for me.
It turned out that while “I want to submit to/interact with Availity programmatically through OpenEMR” was my goal at the time, this was based on a misunderstanding of my own needs.
My actual problem was:
- “I use OpenEMR and I want a way to programmatically submit & manage claims for my single stand-alone clinic because submitting each of these manually through Office Ally and/or Availity is taking far too long and I feel like there has got to be a better way”
The actual solution to this problem (for me) was to get set up to a proper clearinghouse that handles all of these sorts of API connections for me (Availity handles many payers but far from all). For this I’m personally a fan of ClaimRev, but there are a number of options, I know @juggernautsei has done some cool stuff with others like Waystar and Ensora for example.
It took me an embarrassingly long time to figure this out at the start so I figured I would post this in case I can save you or any future reader from going down the wrong rabbit holes like I did.
That being said I’m sure there are many use cases where connecting directly to Availity like this is the correct thing to do, big thanks to everyone in this thread for being so helpful!