# 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:

# Try the Assure demo

The Assure demo 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.

Note: This is a non-production demo.

  1. Go to the Assure demo, (opens new window) and add your email to access the demo.


  1. Go to your eamil and select the one-time linkt to log in.

  2. Once you are logged in, you select the Create dossier button. A dossier is a container that is used to temporarily store information about an end-user that is going through identity proofing:


  1. Click on the dossier link you just created (see blue link in the above image).

  2. From the Create process drop-down menu, select the process you want the end-user to go through. It is possible to have multiple processes within one dossier:


Then just follow the instructions in the selected process flow.

# Set up an API integration

Tip: Before you set up an API integration, it is recommended to familiarise yourself with the most common integration use cases and the OpenAPI documentation (opens new window) 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.

Note: 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 in our demo service documentation.

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, please 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 '' \
--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'
Last updated: 7/12/2021, 3:53:09 PM