Automation

Run collections from the command line, from CI and on a schedule, and reach workspaces through a REST API.

• porticol-cli runs collections, performance tests and flows from files, Postman exports or a server workspace, with the same results as the app's runner.
• JUnit results from porticol-cli, which any CI system reads.
• Monitors run a collection on a schedule and alert by email, Slack, Teams or a signed webhook when it fails and when it passes again.
• Monitors are the one place our servers send your requests. On Porticol Cloud they go through a guard that refuses private, loopback and link-local addresses, and a redirect is never followed.
• Performance runs with virtual users, ramp-up and thresholds, and flows that chain requests with conditions and loops.
• A REST API for collections, environments, runs and monitors, with scoped API tokens and an OpenAPI document.

Other features

• Workbench
• Sending requests
• Local first
• Auth and transport
• Protocols
• Tools
• Collection runner
• Mock servers
• API design
• Sync
• Collaboration
• Shared secrets
• Web client
• Team server
• Identity
• Governance