The registered client ID in your ID.me application must match what you are passing in on your website. Please confirm you are using the correct client ID.
The request must contain only the required parameters. The required parameters for server-side authentication can be found here. The required parameters for client-side authentication can be found here. PLEASE NOTE: Parameters within your redirect URI is not permitted.
The registered redirect_uri in your ID.me application must match what you are passing in on your website. Please confirm you are using the correct URL.
Please see the Documentation. You need to make a POST request to exchange the code for the access token and then make a GET request with the access token to receive the user’s information.
Please see the Documentation. You need to make a GET request with the access token to receive the user’s information. PLEASE NOTE: the access_token is appended to the redirect_uri. Therefore, you should redirect the user again in order to prevent prolonged exposure of the user's access token.
Users cannot complete the flow unless they have satisfied the requirements of the policy (i.e military verification, first responder verification, etc.). Once they are verified, you will first receive the authorization code (server side flow) or access token (client side), which you can then use to make the API call to get the user’s information. Users who are unable to successfully verify will be able to call our customer support hotline that is available within the ID.me verification.
You can retrieve limited data about your API requests by looking into your application API log. PLEASE NOTE: After making the API request, it is best practice to store the JSON response into your CRM tool and/or database.
The logout endpoint is https://api.id.me/oauth/logout. Client ID and redirect URI are required parameters. See example below:
ID.me does not handle promo codes in anyway. Once an API request is made, the partner distributes the offer based on the 'status' of that user.
Test credentials are congifured only for your organization's applications. You will encounter and error if you attempt to authenticate within an application outside of your organization.
When testing, be sure to clear your cache and test in a private browser. In most cases, a previous user is still logged in. PLEASE NOTE: Test credentials typically only carry one affilation. Be sure you are testing aganist the correct policy.
In most cases, your dedicated Integration Engineer will direct you when it is appropriate to request production mode. You can refer to our Production Checklist on the requirements to push to production prior to making your request.