API Reference
Complete REST API documentation for automating Pemvosec and building custom integrations. The API follows RESTful conventions with JSON request/response bodies.
Authentication
Bearer token authentication via JWT. Include token in Authorization header.
RBAC Enforced
All endpoints enforce role-based access control. Ensure your token has required permissions.
Rate Limits
10,000 requests/hour for Essentials, 100,000 for Complete, unlimited for Enterprise.
Base URL
All API endpoints are prefixed with /api/v1 for versioning. The current stable version is v1.
Authentication
Pemvosec API uses Bearer token authentication. Include your JWT token in the Authorization header of all requests.
curl -X GET \
-H "Authorization: Bearer YOUR_API_TOKEN" \
-H "Content-Type: application/json" \
https://api.pemvosec.com/api/v1/aspm/findingsKeep your token secure
Never expose your API token in client-side code or public repositories. Use environment variables and server-side requests.
Endpoint Overview
Authentication
User authentication and session management
Blades
Security blade management across all 16 modules
Findings
Unified findings across all security blades
Antivirus (AV)
Threat detection and malware prevention
EDR
Endpoint Detection & Response
ASPM
Application Security - code scanning, SAST, SCA
Mail Security
Email protection and anti-phishing
IAM
Identity & Access Management
Vulnerability Management
CVE tracking and prioritization
Compliance
Compliance frameworks and reporting
Reports
Report generation and scheduling
Integrations
Third-party integrations
Users & RBAC
User management and access control
Webhooks
Webhook configuration and receivers
Interactive API Documentation
Open Swagger UIInteractive API Explorer
Our full interactive API documentation is available via Swagger UI. Test endpoints, view request/response schemas, and explore the complete API.
What you can do with the API Explorer:
- Test API endpoints with your credentials
- View detailed request/response schemas
- Generate code snippets in multiple languages
- Explore all available API operations
Error Handling
The API uses standard HTTP status codes and returns errors in a consistent JSON format.
| Status Code | Meaning |
|---|---|
200 | Success |
201 | Created |
400 | Bad Request - Invalid parameters |
401 | Unauthorized - Invalid or missing token |
403 | Forbidden - Insufficient permissions |
404 | Not Found - Resource does not exist |
429 | Rate Limited - Too many requests |
500 | Server Error - Something went wrong |
Error Response Format
{
"statusCode": 400,
"error": "Bad Request",
"message": "Validation failed: severity must be one of critical, high, medium, low"
}