Skip to the operations

Identity verification

GBG Go in a decision flow.

1 GBG Go operation a decision flow can call directly, with the credentials your own contract issued. The response is data the rest of the flow reads, branches on, and keeps in the trace.

Category
Identity verification
Type
Integration
Authentication
Token exchange
Test environment
Production host only

What a flow can call

1 operation, each one a step you can place on the canvas.

  1. POST/journey/start

    Start an identity-verification journey

    Starts the GBG journey identified by resourceId and optionally pre-fills identity data.

Provider documentation: https://docs.go.gbgplc.com/docs/go-v1/api-reference/overview

Where it sits in the decision

Identity verification calls have a natural place in a flow.

An identity check gates everything downstream — a score computed against an unverified identity is a score about nobody. These calls sit near the top of a flow, with the branch for a partial or failed match written explicitly rather than left as an exception.

Whatever GBG Go returns is part of the run, so it is part of the record. When someone asks months later why an applicant was declined, the answer cites what came back at the time rather than re-fetching from a service whose answer has since changed.

  • 01Add GBG Go as a connection authenticating with a token exchange.
  • 02GBG Go has one host for both environments, so guard test runs with your own credentials and limits.
  • 03Place a Connection node and pick an operation — “Start an identity-verification journey” is usually the first one a flow needs.
  • 04Map the response into the fields your rules read, then test the whole path before it carries live traffic.

Common questions

Using GBG Go in a flow.

How do I connect GBG Go to a decision flow?

Add GBG Go as a connection in your workspace authenticating with a token exchange, with the credentials your own contract issued — ArboRule calls the provider as you, and never holds a contract on your behalf. Once the connection exists, any flow in the workspace can place a Connection node and choose one of its operations. The credentials live on the connection, not in the flow, so a policy owner can use GBG Go in a decision without ever seeing the secret.

Can I test GBG Go without touching production?

GBG Go exposes one host for both environments, so there is no separate sandbox to point at. Test runs still execute in Sandbox and are recorded separately in decision history, but the call goes to the same place as production — so guard it with your own test credentials, rate limits, or data.

What can a flow call on GBG Go?

1 operation: “Start an identity-verification journey”. Each one is a step you place on the canvas and map into the fields your rules read, and most flows start with “Start an identity-verification journey”. The list comes from the same manifest the engine uses to make the call, so this page cannot describe an operation the product does not have.

Where in a decision should GBG Go be called?

An identity check gates everything downstream — a score computed against an unverified identity is a score about nobody. These calls sit near the top of a flow, with the branch for a partial or failed match written explicitly rather than left as an exception.

Also in Identity verification

Ready when you are

Wire GBG Go into a real decision.

Build the flow in Sandbox, connect your account, and watch the decision pull what it needs before it answers.

Read the docs