Skip to the operations

Business verification

Kyckr in a decision flow.

A Connection node calls Kyckr mid-decision with the credentials your own contract issued. Whatever comes back is data the rest of the flow can read, branch on, and keep in the decision's trace.

Category
Business verification
Type
Integration
Authentication
api_key
Test environment
Separate sandbox host

What a flow can call

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

  1. GET/companies?isocode=$data.company_jurisdiction&name=$data.business_name

    Search a company registry

    Searches one registry jurisdiction by company name.

  2. GET/companies/$data.kyckr_company_id

    Read a company record

    Retrieves a previously discovered company record.

Provider documentation: https://developer.kyckr.com/guides/company-v2/search-for-a-company-if-you-know-the-jurisdiction/

Where it sits in the decision

A provider call is a node, not a side effect.

The call runs where the policy needs it — after the cheap checks that might make it unnecessary, before the rules that depend on it. Calls that do not depend on each other run together rather than in sequence.

Because it is part of the run, the response is part of the record. When someone asks why an applicant was declined months later, what Kyckr returned at the time is in the trace, not re-fetched from a service whose answer has since changed.

  • 01Add Kyckr as a connection, with your credentials.
  • 02Place a Connection node and choose the operation.
  • 03Read the response in the rules, tables and branches that follow.
  • 04Test the whole path in Sandbox before it carries live traffic.

Also in Business verification

Ready when you are

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