redirect_uris
(where the user will be sent after they authorize their health plan data be shared with your app) and securely save your client ID and secret. If you have multiple redirect_uris
you can enter them in a comma separated list like in example below. localhost
redirect with our PROD environments, but can in our sandbox while testing and developing. http://redirect1/callback,http://redirect2/callback,http://redirect3/callback
[email protected]
1up.health with the following information: stand_alone
launch and directly hit our authorization server https://auth.1updemohealthplan.com/oauth2/authorize/test
endpoint. When you hit this endpoint, you will need to include the following query parameters.client_id
: This must contain the client_id of the application you previously registered in the 1upHealth developer console.redirect_uri
: This must contain the redirect_uri
you registered with your application.scope
: The default scope will be user/*.read
. However you will also be able to specify in the query parameter these additional scopes:patient/*.read
and openid
. See more information on scopes here.state
: If you choose to pass a state with the request, the authorization server will simply return it as a query string parameter when redirecting to your application. This parameter is not required but it is recommended that it is used to confirm the validity of a session. See more here.redirect_uri
you registered with your application client ID that you included as a URL parameter above, and will include the OAuth 2.0 auth code passed back as a query parameter. This authorization code expires in 5 minutes.https://auth.1updemohealthplan.com/oauth2/token
endpoint. This authorization code expires in 5 minutes. Below is a sample request where you will need to fill in your app details. ExplanationOfBenefit
and Coverage
resources will not always be reliable and present._include
and _revinclude
as well. See more information on those queries here.