Integrations
APIsec connects to the tools you already run, in two directions: onboarding sources feed APIs into APIsec for testing, and issue trackers and notification channels carry findings out to the people who fix them.
Looking for Hosted Agents? They live under Scanning › Hosted Agents. See Hosted Agents.
Onboarding sources
Three kinds of source feed APIs in. Gateway and platform connections import API definitions directly, with no file handling: Amazon API Gateway, Azure API Gateway, Apigee, Kong, MuleSoft, Boomi, SwaggerHub, and Postman. Traffic-capture formats onboard APIs from recorded requests: HAR, Burp XML, and Mitmproxy. And Surface Code Discovery finds APIs in source code, while Browser Bolt builds specs from a browser session. For choosing between them, see Onboarding Sources.
Issue tracking
Create tickets from findings without leaving the platform, so remediation lands in the backlog your engineers already work from: Jira and Azure DevOps.
Notifications
Send scan results and vulnerability alerts where your team reads them: Slack and Microsoft Teams.
Each page below covers the connection setup, editing, and removal for one integration.
📖 Postman API Gateway
---
📖 MuleSoft API Gateway
Prerequisites
📖 Azure API Gateway
---
📖 Amazon API Gateway
---
📖 Apigee API Gateway
Start adding a new application
📖 Kong API Gateway
Prerequisites
📖 Boomi API Gateway
---
📖 SwaggerHub API Gateway
---
🗃️ Issue Trackers
2 items
📖 CI/CD Integration
Run an APIsec scan from your pipeline and fail the build when serious vulnerabilities exceed the limits you set. This shifts API security testing left: every push or merge request is scanned, and a build cannot ship while CRITICAL or HIGH findings breach your thresholds.
🗃️ Notifications
2 items