Feature

A real API playground, built into your docs

Reading about an endpoint is one thing. Hitting it, watching it respond, and tweaking the parameters until it does what you expect — that's where docs become productivity. Apidex's playground is built for exactly that loop.

A playground, not a curiosity

A lot of tools advertise a “try it” button and then stop short of making it actually useful. apidex treats the playground as one of the main reasons you're here. Every operation is executable, every parameter is editable, every response is rendered with proper syntax highlighting.

Built-in essentials

Every auth flow

OAuth2 (authorization code, client credentials, password, implicit), API keys in headers or queries, bearer tokens, basic auth.

Server variables

Switch between staging, production, or your own dev URL via the server selector — no spec changes needed.

Pretty responses

JSON, YAML, and text responses are formatted and highlighted. Status, headers, and timing are shown alongside.

Smart parameter forms

Generated from your spec: required fields, enums, defaults, descriptions — all surfaced in the right place.

Code samples

Copy a working request as cURL or your language of choice when you're ready to leave the playground.

Local-only credentials

Your tokens and API keys live in your browser. They're never sent to or stored on our servers.

One tool instead of three

Most teams end up with docs in one place, a Postman collection in another, and a wiki page mapping the two. apidex collapses that into a single experience driven by your OpenAPI spec. One source, one URL, one place to learn and try.

Try the playgroundExplore other features