Skip to the operations

Compliance

Vouched in a decision flow.

2 Vouched 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
Compliance
Type
Integration
Authentication
API key
Test environment
Production host only

Who they are

Identity verification from an ID document and a selfie.

Vouched verifies a person by reading a government ID, checking it for tampering, and matching it against a live selfie. It targets onboarding flows that need a document-based check without a manual review queue standing behind it.

What a flow can call

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

  1. POST/api/invites

    Send an ID-verification invite

    Starts Vouched Now, where the applicant completes document and selfie capture on their own device.

  2. GET/api/invites

    List ID-verification invites

    Lists Vouched Now invitations. Useful for reconciling delivery or finding an abandoned invite, but use the callback result as the source of a final verification outcome.

Where it sits in the decision

Compliance calls have a natural place in a flow.

Screening answers the parts of a decision a regulator will ask about, so what matters is not only the verdict but the record of it. A partial match is the interesting case: rarely a decline on its own, and usually the point where the flow opens a case for a reviewer with the match evidence attached.

Whatever Vouched 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 Vouched as a connection authenticating with an API key.
  • 02Vouched has one host for both environments, so guard test runs with your own credentials and limits.
  • 03Place a Connection node and pick an operation — “Send an ID-verification invite” 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 Vouched in a flow.

How do I connect Vouched to a decision flow?

Add Vouched 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 Vouched in a decision without ever seeing the secret.

Can I test Vouched without touching production?

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

2 operations: “Send an ID-verification invite”, “List ID-verification invites”. Each one is a step you place on the canvas and map into the fields your rules read, and most flows start with “Send an ID-verification invite”. 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 Vouched be called?

Screening answers the parts of a decision a regulator will ask about, so what matters is not only the verdict but the record of it. A partial match is the interesting case: rarely a decline on its own, and usually the point where the flow opens a case for a reviewer with the match evidence attached.

Also in Compliance

Ready when you are

Wire Vouched 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