Skip to the operations

Business data

Codat in a decision flow.

2 Codat 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 data
Type
Integration
Authentication
HTTP basic auth
Test environment
Production host only

Who they are

One API over a small business's accounting and banking systems.

Codat connects to the systems a small business already runs — accounting packages, banking, commerce platforms — and normalises what they hold into a single data model. Lenders use it to read a company's own books instead of the figures typed into an application form. The company is based in London and sells mainly to business lenders.

What a flow can call

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

  1. GET/companies

    List connected companies

    Lists companies already created in the Codat client.

  2. POST/companies

    Create a company record

    Creates Codat's container for an SMB's connected accounting, banking or commerce data.

Where it sits in the decision

Business data calls have a natural place in a flow.

Accounting data describes a company's own books rather than its filings, which makes it the input for decisions about trading history and cash position. It arrives after the applicant has connected a source, so a flow reads it where it exists and falls back to submitted figures where it does not.

Whatever Codat 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 Codat as a connection authenticating with HTTP basic auth.
  • 02Codat has one host for both environments, so guard test runs with your own credentials and limits.
  • 03Place a Connection node and pick an operation — “List connected companies” 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 Codat in a flow.

How do I connect Codat to a decision flow?

Add Codat as a connection in your workspace authenticating with HTTP basic auth, 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 Codat in a decision without ever seeing the secret.

Can I test Codat without touching production?

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

2 operations: “List connected companies”, “Create a company record”. Each one is a step you place on the canvas and map into the fields your rules read, and most flows start with “List connected companies”. 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 Codat be called?

Accounting data describes a company's own books rather than its filings, which makes it the input for decisions about trading history and cash position. It arrives after the applicant has connected a source, so a flow reads it where it exists and falls back to submitted figures where it does not.

Also in Business data

Ready when you are

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