Onboarding with Prior Authorization API
Prior Authorization Security and Authorization
Our APIs are compliant with the conventions defined in the OAuth 2.0 specification.
Access control through web tokens
All Optum Enterprise APIs on this platform are secured using JSON Web Tokens (JWT).
Security through TLS
All APIs calls are encrypted over HTTPS. Our APIs support connections using Transport Layer Security (TLS) version 1.2 or later.
Bearer token through OAuth2
Optum uses OAuth 2.0 specification to create a secure connection with our API users, which requires a bearer authorization token to obtain access.
Sandbox
Try our APIs without signing a contract and without any financial obligations by requesting for a sandbox testing environment before using them in your production environment.
NOTE
You should have two sets of credentials:
- One for the sandbox — to help you test our APIs before signing a contract
- One for production — provided after signing a contract or after processing a subscription
These credentials are specific and unique to an API environment and to your company.
NOTE
Optum strongly recommends that you carefully guard your API access credentials. Avoid sharing them with others.
After receiving your client_id and client_secret for the sandbox environment, you can try or test our APIs. For more information, see Readme Prior Auth.
Production
NOTE
If you contract with Optum for API usage, use a separate pair of credentials issued by Optum for your production API environment.
Subscribe to production environment
- To request for a production environment account, reach out to sales @ Prior Autorization team and for the following:
- To either start a new contract
- To have your contract-related questions answered
- If you have an existing account and want to add additional products to it
- Add/remove a product
Prerequisites to use our APIs
Our APIs are private and require credentials to gain access sign up and request for API credentials.
For more information, see Readme Prior Auth.
Updated 9 days ago