The Client Credentials Flow for User Access Tokens is used when your back-end application is authenticating itself on behalf of a user. In this scenario, you pass along your Client ID, Client Secret, and User Identification information.

📘

Note that different APIs may require a different type of Access Token. For instance, most reporting APIs support a service Access Token, but requesting a visit requires a user Access Token.

How It Works

1. Your app authenticates with the WellVia Authorization API using its Client ID, Client Secret, and User Identification information (/oauth/token endpoint).
2. Following validation by the WellVia Authorization API, a response containing an Access Token is provided.
3. Your app uses the Access Token to call the WellVia Platform API on behalf of itself.
4. The WellVia Platform API responds with requested data.
   

Token Expiration

User Access Tokens are set to expire 3 hours from when they were created.

Rate Limiting

There are no limits applied to requesting User Access Tokens. However, any API rate limiting that is applied to your account overall is still considered.