Skip to content
GBG Documents & Biometrics Documentation

Get started

This page takes you from a subscription to a first document processed by AssureID Connect, first in the Workbench and then from your own code. Each step links to the full instructions.

Before you start

Section titled “Before you start”
  • A subscription to AssureID Connect and the user name and password for it, from GBG. A subscription is a licence for a set of features (data capture, authentication, or barcode only); if your user has more than one, you name the subscription in each transaction.
  • The address of the service: the GBG-hosted service, or your own deployment.
  • Images that meet the image requirements: at the least the white-light image of the front of the document, in 24-bit colour, at 300 DPI or more (600 DPI for authentication) and not over-compressed.
  • To integrate from code: the .NET Web SDK, or any HTTP client for the REST API. The SDK and the Workbench are in the AssureID Connect package on the GBG support website.

Steps

Section titled “Steps”
  1. Open the Workbench, log in with your credentials and the service address, and choose your subscription under Options > Subscriptions.
  2. Create a document transaction from a folder of images (sample documents are installed with the Workbench), fill in the device information, and click OK.
  3. Read the results: the document type, the fields read from it and the authentication tests with their dispositions.
  4. Do the same from your code, following the serial workflow: create a document instance, post the front image and any barcode or MRZ data, get the classification, post the remaining images, then get the document result. Processing a document explains each step.
  5. For mobile captures, check the image metrics: ask for a recapture when the glare or sharpness score is under 50.

Check it worked

Section titled “Check it worked”
  • The Workbench shows the classified document type and an overall result of Passed, Failed, Attention or Unknown.
  • From code, a GET on the document instance returns the result. Anything else is explained on the HTTP status codes page.

Next steps

Section titled “Next steps”