Try it in the browser

Every endpoint in the API reference has a Try it button. It sends a real request from your browser to the real API, the same one the curl example beside it makes, and shows you exactly what came back. It loads only when you press it, so reading the reference costs nothing.

Sign in or use a key

Sign in with the account you use for the console. You stay signed in in this browser, the way you do in the console, until the session expires. Signed in, the widget works in sandbox mode only: every request it sends for you is marked sandbox, so it reaches test data and virtual chargers, never a real one.

Paste an API key (flw_ak_…) to call as that key, with its reach and its mode. A sandbox key (flw_ak_test_…) is the way to try requests against virtual chargers from here. The key is kept in this tab only and forgotten when you close it, so it is never left behind on a shared machine.

Forget my credential clears both straight away. A key goes as Authorization: Bearer …; a sign-in as Authorization: DPoP … with a fresh proof from a key your browser holds. Neither is ever shown on the page.

Pick the organization and project

You choose an organization, then a project, every time. Nothing is pre-selected, even when you have only one of each, so the widget never picks a live project for you by default. Changing the organization clears the project.

Confirm every change

POST, PUT, PATCH and DELETE open a dialog before anything is sent. It names the organization and the project by name and id, since two organizations can each have a project called "Depot". Nothing leaves your browser until you confirm; Cancel or Escape sends nothing. Every change asks, every time.

GET requests go straight through, so the dialog stays meaningful for the requests that change something.

What it sends

Authorization, Content-Type: application/json when there is a body, and any header the endpoint declares, such as the Idempotency-Key that commands require, shown as a field to fill in. Nothing else: no cookies and no tracking headers.

What it shows

The status, the response headers and the body, with JSON pretty-printed and anything else shown as text. A body over a megabyte is cut short, with a note saying so.

If the request never reaches Flowion, the widget says so instead of showing a status. Check your connection, or whatever is blocking the request in your browser, before looking for a problem in the API.