Private beta

Let prospects try your API before you finish building it

Selling an API means asking people to believe what your product will feel like. Screenshots and slide decks only go so far, and keeping a live sandbox alive for every prospect is expensive.

Mocktail turns the JSON your API sends or receives into an interactive demo. Your prospect fills in a form, watches the request build itself, and sees the response arrive. No install for them, no sandbox to keep alive for you.

What it does

Paste a payload

Any JSON your API accepts or returns becomes a form. Nested objects stay nested, arrays become dropdowns. No demo code to write.

A live request panel

As someone types, the request JSON updates beside them. Submitting walks through your backend steps and prints the response.

Both paths, live

Flip between success and failure while you present, so the room sees how your API behaves when things go wrong too.

Your branding, either screen

The demo runs in a browser window or a phone frame, carrying your name, your colours and your headline.

Share as a link

The whole demo travels inside the URL. Send it after the call and it still works when they open it on their phone.

Why it works

Teams that sell API products have always needed demos that feel real: solutions engineers preparing them, sales engineers carrying them, founders and product managers who want prospects to experience the product before it is generally available.

The most effective demos have usually been built by hand for each client. At Klarna, dressed-up templates let merchants try Hosted Payment Pages in their own branding before committing to Pay in 3, and gave the sales team a working preview of Open Banking weeks before launch. The same approach carried product conversations at Orbital and Checkout.com.

Mocktail is that practice, productised. What used to take a developer days of hand-building per client now takes minutes, and it stays shareable. The people in the room who do not write code can click through the product themselves instead of trusting your slides.

In practice that means: demos ready when the prospect is, not when engineering is; a clickable artefact to leave behind after the call, still working on a phone; and sales and solutions teams rehearsing on the real product before the product is real.