/api/convert
FroggerAPI converts Postman collections into strict, security-focused OpenAPI 3 specifications. It’s designed to generate specs that Tenable Web Application Scanning (WAS) can consume without a lot of manual fixing or trial-and-error.
- ✔Resolves Postman variables and environments into concrete URLs, params, and examples.
- ✔Infers JSON schemas from request bodies and tightens them (types, maxLength, maxItems).
- ✔Adds basic
patternandformathints for IDs, emails, dates, etc. - ✔Skips
Authorizationheaders so you can keep using Tenable’s credential system.
Once you’ve converted your collection, you can import the generated OpenAPI into Tenable WAS as an API scan:
- 1.In Tenable, go to Scans → New Scan → Web Application and choose the API / OpenAPI template.
- 2.Upload your Frogger-generated OpenAPI file (JSON or YAML).
- 3.Select or configure your API credential as usual (e.g. bearer token, header auth).
- 4.Launch the scan. Tenable will use the stricter schemas and patterns to exercise endpoints more accurately.
If Tenable raised “permissive input validation” issues on your old spec, run those same endpoints through Frogger and re-import the hardened version.
Large language models can guess at an OpenAPI file, but Tenable needs something more predictable:
- ✔ Deterministic output. The same Postman file should always generate the same OpenAPI. Frogger is pure code, not a prompt, so it’s stable and debuggable.
-
✔
Tunable for Tenable. Frogger enforces
maxLength,pattern,format,maxItemsandadditionalPropertiesspecifically to avoid “permissive input” findings. - ✔ Data stays in your environment. Frogger runs as a container or sidecar inside your VPC or on-prem. No Postman collections or environments are sent to an external AI service.
- ✔ Built for CI/CD. The converter is deterministic and scriptable, so you can run it on every build before Tenable scans.
AI is great for improving descriptions and docs after you have a strict spec. Frogger’s job is to generate that strict, Tenable-ready baseline every time.