Skip to main content
POST
Issues a short-lived M2M access token using the client_credentials grant. Use this token as the Bearer credential for Register a user, Send a one-time login/verification code, and Verify a one-time code. This is the first call in the User Registration flow. Permissions: None
string
required
Must be client_credentials.
string
required
Your service client ID.
string
required
Your service client secret.
string
required
API audience: https://api-staging.openloophealth.com for staging, https://api.openloophealth.com for production.
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.