F
froggerapi.io
Dev → Frogger → Security → Tenable WAS
Home Workflow Why Security Docs My specs Account
🐸 Postman → OpenAPI 3.0.1 → harden → CI gate

Submit an API definition Convert Postman to OpenAPI, then harden and enforce before Tenable WAS scans.

Produce strict OpenAPI output from a Postman collection or an existing OpenAPI file. Pro users can save the hardened output to My Specs for history, diffs, scan-ready status, and audit evidence.

Recommended workflow: Convert → Harden → CI gate → Upload to Tenable WAS.
Read the endpoints and CI example →  ·  How this fits Tenable WAS →

Next step: run /api/v1/harden, then enforce with /api/v1/ci/gate before uploading to Tenable WAS.

1) Submit

Upload a Postman collection to generate a normalized OpenAPI 3.0.1 specification. This output is intended for hardening and CI enforcement before security scanning.

Endpoint: /api/convert
Required
Optional
Ready — choose an input and run.
2) Output
OpenAPI 3.x Scan-ready Deterministic
Sample cURL for integrating with this endpoint:
Your OpenAPI spec will appear here after conversion/hardening succeeds.