Skip to the operations

Identity verification

Footprint in a decision flow.

2 Footprint operations 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
API key
Test environment
Production host only

Who they are

Identity verification with a vault for the data it collects.

Footprint runs KYC onboarding — document capture, identity checks and the decision that comes out of them — and keeps the personal data it collects in an encrypted vault its customers call rather than copy. The point is that the sensitive fields never have to land in your own database to be usable.

What a flow can call

2 operations, each one a step you can place on the canvas.

  1. POST/onboarding/session

    Start an identity-verification session

    Creates a short-lived token for Footprint's browser or mobile SDK.

  2. GET/users/$data.footprint_user_id

    Read an identity-verification result

    Reads the current status for a Footprint user. A pending or manual-review result is not a pass; accept the final outcome via a verified Footprint webhook or this follow-up call.

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 Footprint 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 Footprint as a connection authenticating with an API key.
  • 02Footprint 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 session” 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 Footprint in a flow.

How do I connect Footprint to a decision flow?

Add Footprint as a connection in your workspace authenticating with an API key, 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 Footprint in a decision without ever seeing the secret.

Can I test Footprint without touching production?

Footprint 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 Footprint?

2 operations: “Start an identity-verification session”, “Read an identity-verification result”. 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 session”. 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 Footprint 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 Footprint 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