API: Creating Zuub Specific Payer Credentials
Zuub's asynchronous product streamlines access to patient benefit breakdowns by securely navigating payer portals.
Overview
Asynchronous requests go directly to payer portals to retrieve patient benefits and eligibility. Similar to if a human was manually pulling this information, asynchronous requests require payer credentials to sign into the portal and access data.
For security purposes, many payer portals now require two factor authentication (2FA). For payers that require 2FA, Zuub is unable to share credentials with the office and Zuub specific credentials are required to be created.
For payers that do not require 2FA, Zuub is able to share credentials with the office. However, this can be challenging due to offices frequently updating credentials and payer portals requiring new passwords. Therefore, Zuub specific credentials are recommended but not required.
Below is an overview of the credential creation process:
- Generate the below assets for a specific payer via the portal registration API:
- Email address
- Phone number (if the payer only supports SMS 2FA)
- Use the provisioned email address and phone number (when applicable) to create a Zuub specific credential for the payer portal.
- Enable 2FA, if applicable.
- Finalize account setup.
- Zuub specific account creation is complete!
Step by step guides on how to create Zuub specific credentials for the top payers are listed below.
2FA Payers: Zuub Specific Credentials Required
- Aetna
- Ameritas
- Availity
- BCBS FEP
- BCBS of Alabama
- BEAM
- Cigna
- Delta Dental
- Dental Insurance Company
- Delta Dental Toolkit
- Delta Dental of Massachusetts
- Dental Hub (Skygen)
- Dentaquest/Sunlife
- Denti-Cal
- GEHA
- Guardian
- Lincoln
- Metlife
- Mutual of Omaha
- One Healthcare
- UMR
- Unum
Non-2FA Payers: Zuub Specific Credentials Recommended
This resource was updated 11/14/2025.