JSON and EDI-X12 formats available
It can receive and return client data in either X12-278 or JSON over HTTPS. We’ll return the data in the same format the client used to send the transaction.
Both EDI and portal payers available
Our system is connected to EDI/direct payers and a wide range of web portal payers. The API is also responsible for payer-specific requests and request transformation.
UM vendors available for authorization inquiries
We’re connected to all major UM vendors for radiology services in addition to most of the major medical connections.
Returns 13 authorization statuses
We’ll return a variety of 278 certification action codes that represent the payer’s authorization status, which users can then interpret to understand the status. These codes represent common statuses, such as approved, partially approved, pending and denied, plus other error messages.
Developer resources
Prior Authorization Inquiry API
Q: How can I test it in the sandbox?
A: Our team can create an account for you to test the API in our sandbox. We have a few pre-written responses, that are not from payers, so you can see how the responses appear.
Q: How long will it take for us to set up your system and use your API?
A: You’ll need to send the data according to our API contract and handle the responding data. Our implementation team will need to work with your client to map their payer IDs to our system's payer ID.
Q: Does the Inquiry Authorization check for status daily automatically?
A: No, the Inquiry API checks synchronously upon a request. It’s in the 2025 roadmap to automatically check the status daily until the authorization date of service, or until the authorization has reached its terminal status (approved, denied).
Marketplace updates
Subscribe to The Spark
We're adding new products and services to rapidly expand our marketplace and the potential is huge. Be an early adopter and stay ahead of the trend with our bi-weekly e-updates.
Your account is almost complete! To quickly access your account,