Skip to the operations

Business verification

Middesk in a decision flow.

2 Middesk 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
Business verification
Type
Integration
Authentication
API key
Test environment
Production host only

Who they are

Business identity verification from US public records.

Middesk verifies US businesses against Secretary of State filings, IRS records, watchlists and other public sources, and returns a structured verdict on whether the entity, its address and its officers check out. It also handles state tax and payroll registration for its customers.

What a flow can call

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

  1. POST/v1/businesses

    Verify a business name and address

    Starts an asynchronous US business-verification order.

  2. GET/v1/businesses/$data.middesk_business_id

    Read a business verification

    Polls a business created by Verify a business name and address.

Where it sits in the decision

Business verification calls have a natural place in a flow.

Company checks answer whether the entity applying exists, who controls it, and whether its filings support the application. They usually run early: if the company cannot be verified, most of what follows is moot, and the flow can decline or refer before spending on anything else.

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

How do I connect Middesk to a decision flow?

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

Can I test Middesk without touching production?

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

2 operations: “Verify a business name and address”, “Read a business verification”. Each one is a step you place on the canvas and map into the fields your rules read, and most flows start with “Verify a business name and address”. 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 Middesk be called?

Company checks answer whether the entity applying exists, who controls it, and whether its filings support the application. They usually run early: if the company cannot be verified, most of what follows is moot, and the flow can decline or refer before spending on anything else.

Also in Business verification

Ready when you are

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