# 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 information about different service providers, see Identity proofing services (providers).
- 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 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.
To try it out, open the Assure demo, http://labs.signicat.com/assure-test-server/ (opens new window). Here is an image slider showing how to get started with the demo:
For explanations of basic terms used in this user interface, e.g. dossier and process, see Key concepts.
# 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 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, 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'