Air Pipe ships a request client, so you don't reach for a separate app to hit your endpoints. Save requests into collections, fire them at your live deployment, and attach assertions that pass or fail on every run — with the requests and their tests stored in the platform, not on someone's laptop.
A request client that already knows your API
Build and save requests the way you'd expect — method, URL, headers, query params and body — organised into collections and folders. Seed a request straight from an interface in your deployed config, so you're testing the endpoint you actually shipped rather than retyping it.
Collections and folders for your saved requests
One-click seed from your deployed config's interfaces
Bearer, Basic and API-key auth, with {{variable}} placeholders
Assertions that pass or fail on every run
Attach checks to a request and Air Pipe evaluates them each time it runs, against the response status, body fields and headers. A run comes back green or red with a count of what passed and failed — so a saved request doubles as a regression test, not just a one-off call.
Assert on status, body.* and headers.*
Conditions like equals, contains, regex, is a UUID, greater / less than
Pass / fail result with passed and failed counts
The same checks that guard your endpoints
The assertion conditions your tests use are the same ones Air Pipe runs inside a config's assert block on live traffic. A test isn't a separate testing language to learn — it's the runtime's own validation, pointed at a saved request and recorded.
Runs on the server, recorded every time
Requests run server-side against your staging or production deployment — no browser CORS, no local proxy — and every run is kept with its status, HTTP code, latency and time. Because the collections live in your organization, your team sees the same requests and the same history.
Run against staging or production deployments
Server-side execution, not from your browser
Run history per request, shared across your org
Frequently asked questions
Is this a replacement for Postman or Bruno? For testing your Air Pipe APIs, largely yes — you get a request client with saved collections, variables and auth without installing anything. The difference is that the requests and their assertions live in your Air Pipe organization, run server-side against your deployments, and are shared with your team.
Where are my saved requests and tests stored? In your Air Pipe organization, alongside the config they test — not in a local app or a personal cloud account. Anyone on the team with access sees the same collections and the same run history.
What can an assertion check? The response status, any field in the body, and any header — using conditions such as equals, not-equals, contains, starts/ends with, regex, is-a-UUID, is-an-array, is-null and numeric greater/less than. Each request can carry several, and they're evaluated together on every run.
Where do the tests actually run? Server-side. Air Pipe runs the request against your selected deployment and evaluates the assertions there, so there's no browser CORS to fight and no local runner to keep alive. The result and timing are recorded in the request's run history.
Can I test against staging and production? Yes. Pick the environment on the request and it runs against that deployment. Variables let you keep the same request pointed at different environments without rewriting URLs or tokens.