After starting a journey, you receive anDocumentation Index
Fetch the complete documentation index at: https://docs.go.gbgplc.com/llms.txt
Use this file to discover all available pages before exploring further.
instanceUrl in the response. Share this URL with the end user to begin the verification experience. The GBG hosted journey handles everything from this point, including device authentication, identity verification, UI (user interface) rendering, and data submission are all managed automatically.
Your backend does not need to call any other endpoints until you are ready to fetch results.
Share the instance URL
Share theinstanceUrl with the end user using a delivery method of your choice. For example:
- Redirect: Redirect the end user directly from your application to the URL.
- Email or SMS: Send the URL to the end user via email or text message.
- In-app link: Display the URL as a button or link within your application.
- QR code: Generate a QR code from the URL for the end user to scan.
GBG GO does not deliver the URL to the end user on your behalf. You are responsible for sharing the URL with the end user through your chosen delivery method. The above examples are suggested approaches, but you can implement the delivery in any way that fits your application’s architecture and user experience.
Server-side redirect
The simplest approach for web applications. Your backend starts the journey and immediately redirects the user:Return the URL to a frontend client
For single-page apps or mobile clients, return the URL as JSON and let the client handle navigation:Send via email or SMS
For asynchronous flows where the end user completes verification later:Node.js
What the end user experiences
Once the end user opens theinstanceUrl, the hosted journey guides them through the verification steps configured for the journey. This includes:
- Identity data collection
- Document capture
- Biometric verification
The
instanceUrl is time-limited. Share it with the end user promptly after receiving it from the API response.