Promaster APIs
A docs platform that turns OpenAPI and Postman collections into a searchable reference — every endpoint with request/response schemas, and a playground that reuses the auth token in the browser.
Overview
Promaster APIs is the public contract for the product: hundreds of endpoints, grouped, searchable, tryable. I built it on a format-agnostic docs monorepo — OpenAPI, Postman, Swagger, Insomnia, Apidog parse into one NormalizedDoc, then a Next.js renderer never talks to the raw spec.
Engineers browse the catalog by group and path, read typed request and response schemas next to the method, and send a live call from the same page with Bearer auth from this browser. Search is client-side and fast. JSON viewers, code samples, and markdown sit on shared packages so Bolesa WMS, shipping docs, and Promaster ship from one platform.
The live site is generated from the collection, not a wiki. 683 endpoints across 71 groups stay in sync with the spec because the parser is the source of truth — not a hand-maintained markdown tree.
Outcomes
The capabilities that matter in a walkthrough — what a team can actually run.
- 01The spec is the docs — OpenAPI and Postman parse into one model, so the reference cannot drift from the collection
- 02Every endpoint is a contract — request and response schemas sit next to the path, typed, not a prose guess
- 03Try it in the browser — playground calls reuse your auth token, HTTPS, no Postman round-trip to prove a route works
- 04Search the catalog — groups, methods, and paths in one index so 683 endpoints stay findable
- 05One platform, many APIs — shared parser, renderer, playground, and theme across Promaster and the Bolesa docs apps
- 06Format-agnostic — Swagger, Insomnia, Apidog, and Postman all land on the same NormalizedDoc
- 07A desk for operators — browse, read the contract, send a live call — the three moves an integrator actually makes
- 08Live reference — generated docs at promaster-docs.vercel.app, not a stale Confluence export
Tell me about your product
Share a short brief — problem, timeline, and stack — and I'll reply with a candid view on fit, effort, and the fastest path to a shippable milestone.