Skip to main content
POST
Issues a new patient access token (and rotated refresh token) using the refresh_token grant, without requiring the patient to log in again. See “Keeping the session alive” in the User Registration guide. Permissions: None
string
required
Must be refresh_token.
string
required
Refresh token from a previous Exchange a verification code or refresh call.
string
required
Must be the same client the refresh token was issued to.
string
required
Your client secret.
object
required
string
required
Correlation id echoed on every response.

Body

application/json

Fields required depend on grant_type: client_credentials also requires audience; the verification-code grant also requires code; refresh_token also requires refresh_token.

grant_type
enum<string>
required
Available options:
client_credentials,
urn:openloophealth:oauth:grant-type:verification-code,
refresh_token
client_id
string
required
client_secret
string
required
audience
string

Required for the client_credentials grant.

code
string

Verification code from POST /auth/verify-otp. Required for the verification-code grant.

refresh_token
string

Required for the refresh_token grant.

Response

OK

data
object
required
request_id
string<uuid>
required

Correlation id echoed on every response.