API Documentation
Access our comprehensive CVE vulnerability database programmatically. RESTful API with JSON responses for CVE lookups, search, and security monitoring.
🔑 Get API Access
To use our API, you need an API key. Registration and API access are free, but require admin approval to prevent abuse.
Create Free Account & Request API AccessAuthentication
All API requests require authentication using an API key. Include your API key in the Authorization header:
Rate Limits: 1000 requests per hour. Contact us if you need higher limits.
Base URL
Endpoints
GET /cve/{cve_id}
Retrieve detailed information about a specific CVE.
Parameters
| Parameter | Type | Description |
|---|---|---|
| cve_idREQUIRED | string | CVE identifier (e.g., CVE-2024-1234) |
Example Request
Example Response
GET /cves/search
Search CVEs by keywords, severity, vendor, or date range.
Query Parameters
| Parameter | Type | Description |
|---|---|---|
| q | string | Search query (keywords) |
| severity | string | Filter by severity: CRITICAL, HIGH, MEDIUM, LOW |
| vendor | string | Filter by vendor name |
| year | integer | Filter by publication year (e.g., 2024) |
| page | integer | Page number (default: 1) |
| limit | integer | Results per page (default: 50, max: 100) |
Example Request
GET /cves/recent
Get recently published CVEs.
Query Parameters
| Parameter | Type | Description |
|---|---|---|
| days | integer | Number of days to look back (default: 7, max: 90) |
| severity | string | Filter by severity |
| limit | integer | Results per page (default: 50, max: 100) |
GET /stats
Get database statistics including total CVEs, severity breakdown, and recent trends.
Example Response
Error Codes
| Code | Description |
|---|---|
| 400 | Bad Request - Invalid parameters |
| 401 | Unauthorized - Invalid or missing API key |
| 404 | Not Found - Resource doesn't exist |
| 429 | Too Many Requests - Rate limit exceeded |
| 500 | Internal Server Error - Something went wrong |
Support & Questions
Need help or have questions about the API? Contact us or check the FAQ.