Feature

Password-protected API documentation, without accounts

Some docs are for the world. Others are for one client, one partner, one hire. Apidex lets you share both kinds with the same simple link — and a password when privacy matters.

Privacy without the bureaucracy

Most tools that offer private documentation make you build a user system around it: accounts, roles, seats, billing. That works for big enterprise portals, but it's overkill when you just need to send your API spec to one integration partner.

apidex keeps it simple. You set a password when you create a shareable link. The link still works for everyone — they just need the password to load the docs. That's the whole flow.

How it works

Salted password hashing

We never store your password in plain text. Only a salted hash is kept, so even we can't read it.

One link, one password

Share the URL however you want — Slack, email, a doc — and share the password through a separate channel.

Revocable in one click

Remove the spec at any time and the link stops working immediately.

Same UX, fully private

Visitors get the same polished docs and playground — they just unlock it once.

When to use it

Sharing a partner integration before launch. Sending a draft spec to a contractor. Giving a candidate a take-home that touches a real API. Any moment where you want a polished docs link, but you don't want it on the open web.