Skip to the operations

Identity verification

idwall in a decision flow.

2 idwall 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

Brazilian identity verification and background checks.

idwall verifies who someone is against Brazilian public records, court filings and watchlists, and packages the result as a report rather than a stream of raw data. Its customers are banks, fintechs, marketplaces and mobility platforms doing onboarding at volume. Each customer contracts a "matriz" that decides which checks run, so two accounts calling the same endpoint get different work done.

What a flow can call

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

  1. POST/relatorios

    Start a background check (create a report)

    Creates a report and starts the checks in it.

  2. GET/relatorios/$data.idwall_report_number

    Read a report's result

    The current state and findings of one report. Reports are processed asynchronously, so this is the read a flow makes when it resumes rather than immediately after creating one.

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 idwall 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 idwall as a connection authenticating with an API key.
  • 02idwall 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 a background check (create a report)” 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 idwall in a flow.

How do I connect idwall to a decision flow?

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

Can I test idwall without touching production?

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

2 operations: “Start a background check (create a report)”, “Read a report's 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 a background check (create a report)”. 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 idwall 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 idwall 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