Coming 2027

Test the chain, not just the call.

Luvin turns your OpenAPI and AsyncAPI contracts into visual API journeys, writes the Arazzo for you and tests every step of the chain, against your API or in simulation.

Local-first. No account. Nothing leaves your machine.

The problem

Stop calling A to test B.

A single screen of your app usually depends on several APIs called in order. Log in on A to get a token, call B with it to get the customer, call C with the customer’s id. To test C, you call A and B by hand and copy values between responses. Every time. And nobody can quickly say which APIs that screen depends on, or how the data moves between them.

Today you call A, copy the token, call B, copy the id and call C by hand. With Luvin the journey runs the whole chain and passes the data.

Luvin removes those manual calls and makes your integrations visible.

How it works

From API requests to complete API journeys.

  1. 1

    Bring your contracts

    Add the OpenAPI and AsyncAPI files of the APIs involved, or open a folder that already has them.

  2. 2

    Draw the journey

    Drag operations onto a canvas. Tokens, ids and fields are wired between steps by rules, no AI involved.

  3. 3

    Get the Arazzo

    The canvas writes a standard Arazzo file, validated against the contracts as it changes.

  4. 4

    Test the chain

    Run generated and custom cases against the real API or in simulation, with verdicts in plain words.

Draw it once

Each operation you drop becomes a step. A customerId connects to the id returned by “create customer”, and anything nobody feeds becomes an input of the journey.

The visual builder with the operation palette, wired steps and the detail of a step

Test the whole chain

Happy path, invalid inputs, calls without credentials and every documented error path, generated from the contracts and explained in plain words.

Generated test cases next to the results of a run against a real API

The Arazzo stays yours

The canvas edits a real Arazzo file: review it in a pull request, keep it in git and run it with any Arazzo tool.

The Arazzo editor with live validation next to the results

Compare

Keep your API client for single requests. Use Luvin for the chain.

API clients are great at single requests, and all of them can chain calls. The difference is what it takes to build the chain, see it and prove it works.

—LuvinPostmanBrunoInsomnia
Built aroundJourneys across several APIsSingle requests and collectionsSingle requests and collectionsSingle requests and collections
Passing data between callsWired automatically from the contractsScripts or a FlowScripts (bru.setVar)Response template tags
Seeing how data flowsA diagram of every API, step and fieldRead the scripts, or build a FlowRead the scriptsOpen each request’s tags
Negative casesGenerated from the contractTest scripts you writeTest scripts you writeTest scripts you write
What you keepArazzo, an open standardA Postman collectionBruno files in gitAn Insomnia export

What about Postman Flows?

Postman Flows gives you a canvas to build a chain. Luvin reads your contracts, builds the chain and tells you if it works.

See the full comparison →

Based on each product’s public documentation as of November 2026. Postman, Postman Flows, Bruno and Insomnia are trademarks of their respective owners; Luvin is not affiliated with them.

Features

Everything the chain needs, in one place.

No more manual chains

Luvin calls every API in order, passing tokens, ids and any field from one step to the next.

See your integrations

Which APIs take part, in what order, and which response field feeds which parameter.

Failures in plain words

“status is INACTIVE but ACTIVE was expected”, with the step and field highlighted.

REST and events

Mix HTTP calls with AsyncAPI send and receive steps in the same journey.

Per-API authorization

OAuth 2.0 and more, set per API or per journey, without touching the Arazzo.

Local and in git

No backend, no account. Workspaces are plain files; secrets stay encrypted on your computer.

Who it’s for

For teams whose apps depend on chains of APIs.

Integration and QA engineers

Who test chains of API calls by hand today and want generated negative cases and clear verdicts.

API product and partner teams

Who need to show that journeys across several APIs work end to end, with a report to share.

Product managers

Who want to try a journey with their own data in a simple interface, without test code.

API designers

Who want to see how their APIs connect and validate journeys before anything is built.

Be the first to test the chain.

Luvin launches in 2027. Join the waitlist for early access and the first pilots.

We’ll only use your details to tell you about Luvin. No spam.