Upon completing the Provisioning Request below, you will be supplied with a group-specific, registration link which can be disseminated to your users to create accounts. This link will automatically open a dialog box with your group auto-selected (see the User Interface section below for more details). Your users will then enter their individual “human-readable” identifiers (typically their member number/ID).
The memberIdentifier will then be passed to your web service endpoint which must be SSL encrypted. Your system will then determine whether the identifier is valid.
If the memberIdentifier is valid, your service passes back "isValid" : true as well as values for fields denoted as REQUIRED.
If the memberIdentifier is NOT valid, then your service passes back "isValid" : false. The user then can re-enter their identifier or contact your group for help.
Please note that self-signed SSL certificates will not work and cause an error.
Group-Specific Registration Links
Depending on which system you are integrating with, you will append the token we will provide to the URLs as part of the query string. This will auto-select your group from the list. You can optionally also pass in the memberIdentifier by using &memId and the corresponding value. This will auto-populate the member number/ID.
To find the URL for the system you are integrating with:
Find the section for the User Verification API info.
Using the group-specific registration link, the user is presented with a screen with your group automatically selected.
If the memberIdentifier is valid, the user is asked to review their information and check a box certifying their identity.
The user will then finish creating their account by filling out the rest of the registration form.
Supported Authentication Methods
You will provide us with an access_token_name and access_token_value with which to pass via HTTP Header.
OAuth 2.0 - Client Credentials
We currently only support the grant_type of client_credentials. The service must provide the authorization server’s token endpoint, client_id, and client_secret. See OAuth 2.0 Client Credentials for more details.
The endpoint we will deliver activity progress data.
The endpoint of the service that will receive the request for an access token.
A public identifier.
A secret known only to the application and the authorization server.
HTTP/1.1 400 Bad Request
"error_description": "Request was missing the 'redirect_uri' parameter.",
"error_uri": "See the full API docs at https://authorization-server.com/docs/access_token"