Grab an API key
Generate a scoped key and send it in the x-api-key header. No OAuth dance to start, no waiting on a sales call. You are talking to the API in the time it takes to copy a header.
Developers & API Partners
Become a Loopfour developer partner.
The Loopfour Workflows API lets you build finance automation directly into your own product. Trigger runs, wire up agents and connections, react to webhooks, and read back structured tables and full run evidence. If your team builds software for finance teams, this is how you plug their operational work into ours.
API documentation
The full API is documented and public.
No gated PDF, no "contact us for the spec". The reference covers authentication and every resource you will call, with the request and response shapes laid out. Start with the quickstart, then keep the reference open in a tab.
- Workflows: define the automation graphREST
- Runs: execution plus full audit evidenceREST
- Agents: AI-assisted steps inside a workflowREST
- Connections: authenticated integration accessREST
- Webhooks: react to provider eventsREST
- Tables: structured operational dataREST
How it works
Three steps from key to running workflow.
Build a workflow
Define the graph once: triggers, actions, agents, and the connections they run against. The workflow is the contract. Your code decides when to run it and what to feed it.
Run & read the evidence
Kick off runs from your app and pull them back to see exactly what happened. Every run records the trigger, actions, approvals, exceptions, and outputs, so you are never guessing.
Partner benefits
What you actually get when you build on Loopfour.
A real API, not a form wrapper
Workflows, runs, agents, connections, webhooks, and tables are all first-class REST resources. If you can call an endpoint, you can drive the whole automation layer from your own product.
Every run is auditable
Runs are not fire-and-forget. Each one keeps the full record of what triggered it and what it wrote, so your customers and their auditors get evidence instead of a shrug.
Scoped, governed execution
Keys are scoped and workflows run inside a controlled environment. You decide what a partner integration can reach, and approvals stay in the loop where they matter.
Ship in an afternoon
The quickstart gets a first workflow running in about five minutes. From there the reference covers every resource you will touch, with request and response shapes you can trust.
Built for builders
Made for people who read the docs before the pitch.
AI-driven automation you can steer
Agents handle the judgment-heavy steps inside a workflow, but they run as defined steps you configure and inspect. It is automation with the reasoning shown, not a black box you have to trust blindly.
Tailored control per integration
Connections hold the authenticated access to the systems a workflow touches. Grant exactly what a run needs and nothing else, and swap credentials without rewriting the workflow.
Documentation that keeps up
The API reference tracks the real endpoints: authentication, workflows, runs, agents, connections, webhooks, tables, and secrets. Read it once and you know the surface.
Support that speaks developer
Webhooks let your systems react to provider events the moment they land. When you need a hand wiring it up, you reach people who know the runtime, not a ticket queue.
See it run before you write a line of code.
Book a demo and we will walk through the API, a live workflow run, and the evidence it leaves behind. Bring the integration you have in mind and we will map it out with you.
Book a demo