Skip to the operations

Compliance

ComplyAdvantage in a decision flow.

3 ComplyAdvantage 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

AML risk data: sanctions, PEP and adverse-media screening.

ComplyAdvantage builds and maintains a financial-crime risk database — sanctions lists, politically exposed persons, watchlists and adverse media — and sells screening and ongoing monitoring against it. Its customers are regulated firms that have to evidence who was screened and what came back.

What a flow can call

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

  1. POST/searches

    Screen a person

    Creates a sanctions, PEP and adverse-media search for one applicant.

  2. GET/searches/$data.complyadvantage_search_id/details

    Read a screening result

    Fetches the complete result for a previous search, including matched entities and their sources.

  3. GET/searches

    List past screenings

    Lists searches already made by the account. Filter and paginate with query parameters on the node instead of fetching the entire history.

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

How do I connect ComplyAdvantage to a decision flow?

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

Can I test ComplyAdvantage without touching production?

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

3 operations: “Screen a person”, “Read a screening result”, “List past screenings”. Each one is a step you place on the canvas and map into the fields your rules read, and most flows start with “Screen a person”. 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 ComplyAdvantage 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 ComplyAdvantage 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