Docs for the Engineers Who Actually Call Your API

Not every API needs a public-facing docs site. Internal microservices, admin-only endpoints, and services that only ever get called by other teams inside the company still need documentation — just for an audience of engineers who already have network access, not for outside developers evaluating whether to integrate.

Where this actually fits

The common case: your organization has a handful of internal tools already — an admin panel, an internal developer portal, a tab inside an existing ops dashboard. GetMan is a single script tag, so it drops into whichever of those already exists as a new route or embedded panel, rather than requiring a dedicated docs deployment and its own hosting, TLS certificate, and access controls.

<div id="api-docs" style="height: 100vh"></div>
<script src="https://cdn.getman.dev/latest/getman-ui.js"></script>
<script>
  GetMan.launch(document.getElementById('api-docs'), {
    url: 'https://internal-service.your-network/openapi.json',
  });
</script>

The microservices problem

Once a team has more than a couple of services, each one often exposes its own auto-generated docs route using whatever its framework defaults to — one service shows FastAPI’s Swagger UI, another shows springdoc-openapi’s default page, another has no docs UI at all because Express doesn’t ship one. If your services already generate an OpenAPI document, see the framework-specific guides for pointing GetMan at it instead: FastAPI, NestJS, Spring Boot, Express, and Laravel. The result is the same explorer, the same keyboard shortcuts, and the same navigation regardless of which service someone’s currently looking at — engineers learn one tool instead of relearning each service’s default.

No public exposure required

Everything renders client-side in the visitor’s browser, so the page hosting GetMan never needs to be reachable outside your network. The spec URL you pass to GetMan.launch() can point at an address that only resolves on your VPN — there’s nothing in how GetMan works that assumes or requires a public audience.

Combined with self-hosted API documentation, this covers the two things internal tooling usually needs: staying off the public internet, and staying out of any third party’s hands.