# Quick start guide for Assure
This quick guide describes how to try out Signicat's identity proofing solution, Assure, using the following approaches:
If you want to read more before trying it out, we recommend the following topics:
- For high-level introduction topics, see Use case: Onboarding a new customer and Identification services overview.
- For term descriptions used in the Assure API, see Key concepts.
- For detailed information about all available endpoints and properties, see the OpenAPI documentation.
# Try the Assure demo
The Assure demo (opens new window) allows you to test a subset of the Signicat Assure functionality (apps). It is not a product on its own but it integrates with the Assure API. This is an easy way to get an initial impression of what you can do with Signicat Assure.
The Assure demo is a non-production tool. We have created it for testing and demonstration purposes. It is just an example of how the verification flow could be implemented using the different SDKs. The screens you see in the provider flow (C) will probably look differently in your own implementation.
The Assure API can be used either in a web or in a native (mobile) context. In this section, we show images from the Assure demo in a web environment.
The following steps show a typical user flow where we use Onfido's native SDK to take a photo of an ID document and a selfie to match those images.
The steps are divided into the following main parts:
- A: Create dossier and process
- B: Configure the provider
- C: Follow the provider's verification process
- D: Inspect the result manually
# A: Create dossier and process
You can access the Assure demo from this link:http://labs.signicat.com/assure-test-server/ (opens new window).
Once your are logged in, you can create a dossierfor the end-user information:
Inside the dossier, you create a process for the identity verification:
- If you want to test with Electronic IDentification, please contact Signicat at firstname.lastname@example.org to be added as an agent on their registration authority application. This is necessary for your verification requests to be manually approved by someone (which is a step that is required by Electronic IDentification).
- ReadID and FaceTec are not available for web in the Assure demo. Instead, you must download the native mobile app to run on your Android or iOS device (select the download button at the top of the Assure demo screen).
# B: Configure the provider
In this example, we have selected Onfido's native SDK. We want to take a photo of an ID document and a selfie to match those images.
You can keep most of the standard settings, as in the following example (see more details below the image):
- Process type: We have chosen Document + Selfie since we want to take a photo of an ID document and a selfie to match those images. The available process type options vary from provider to provider. For a full overview, see the
processTypedescription in the OpenAPI documentation.
- Native means using Onfido's own SDK instead of Signicat's own Capture UI.
- Redirect means the user is redirected to a web browser to perform the verification, instead of verifying with the QR code on a mobile device.
# C: Follow the provider's verification process
After you have set up the provider (here Onfido) in the Assure demo, you are now redirected to the provider's web SDK view and are asked to verify your identity. Then you can just follow the instructions on the provider-specific UI.
# D: Review the result manually
After the verification is complete, you are redirected to the Dossier page in the Assure demo and can review the result manually:
Here you can immediately see the status of the process (
You can also inspect the result in more detail by clicking the Process id link. Here, you can see the provider specific information with the results from the analysis:
# Set up an API integration
Before you start the integration
Before you set up an API integration, it is recommended to familiarise yourself with the most common integration use cases (see for example the Onfido use case in the Provider-specific section) and the OpenAPI documentation to learn about available endpoints and their properties.
This is the most flexible way of testing Signicat Assure. You can use your preferred IDE, Framework, Postman, etc. using credentials provided by Signicat Operations or using the demo-service credentials available on the Demo service page.
The Demo service is a shared environment that anyone can access. Ensure that you DO NOT use or provide anything that contains PII data.
# Client credentials
To access the Assure API, you must use your set of credentials provided by Signicat Operations.
If you just want to try out the API, you can use the demo service credentials available on the Demo service page.
Note: The demo service is a shared environment that anyone can access. For that reason, DO NOT use or provide any PII data using the demo-service credentials.
# OIDC token
After you have the credentials, you must acquire an access token using the OpenID Connect (OIDC) protocol. This is a procedure required to consume the Signicat REST services. For more information on how to do this, see Accessing Signicat REST Services.
Make sure to add the client.assure.api and client.capture.api scopes to your token request. This is a cURL example of an OIDC token request:
curl --location --request POST 'https://preprod.signicat.com/oidc/token' \ --header 'Content-Type: application/x-www-form-urlencoded' \ --header 'Authorization: Basic <BASE64 ENCODED CLIENTID:CLIENTSECRET>' \ --data-urlencode 'grant_type=client_credentials' \ --data-urlencode 'scope=client.assure.api client.capture.api'