Swagger Integration with Snapsec ASM
Use the Swagger integration to automatically ingest API endpoints into Snapsec ASM by uploading or onboarding your OpenAPI/Swagger specification files.This integration helps ensure complete API visibility across your attack surface.
1. Prerequisites
Before importing your API specifications, ensure you have:- A Swagger/OpenAPI file (
.jsonor.yaml). - Valid API definitions with paths, methods, and metadata.
- Access to Snapsec ASM with permission to install integrations.
2. Enable Swagger Integration in Snapsec ASM
- Navigate to ASM → Integrations.
- Locate Swagger in the integrations list.
- Click Install to enable the adapter.
3. Import Swagger / OpenAPI Specification
After enabling the integration:- Open ASM → API Catalog.
- Click Import Swagger.
- Upload your specification file (
.yamlor.json). - Snapsec will automatically parse:
- API endpoints
- HTTP methods
- Parameters
- Descriptions
- Security schemas
4. Supported File Formats
Snapsec supports:- OpenAPI v2 (Swagger 2.0)
- OpenAPI v3.x
- JSON and YAML formats
5. What Gets Imported
From your Swagger definition, Snapsec ASM extracts:- Endpoint paths
- Methods (GET, POST, PUT, DELETE, etc.)
- Tags and grouping
- Query/body parameters
- Authentication requirements
- Descriptions and summaries
6. Updating Swagger Specifications
If your APIs evolve:- Upload a new version of your Swagger file.
- Snapsec will automatically:
- Add new endpoints
- Update changed endpoints
- Mark removed endpoints as deprecated
Troubleshooting
- Validation Failed: Ensure your Swagger/OpenAPI structure follows official schema.
- Missing Endpoints: Check if they are inside the
pathsobject. - Upload Error: Confirm the file format is
.jsonor.yaml.
Snapsec ASM uses the Swagger integration to maintain accurate, continuously updated API inventories across your environment.