Exporting Compliance Data
The compliance endpoints of the REST API give read access to your CRA compliance data. They need an API key with the read scope. next-task and next-deadline work on the Reporting plan or higher. The other endpoints need the Enterprise plan. See API Overview.
| Endpoint | Returns |
|---|---|
GET /api/v1/compliance/status | The compliance status of your company |
GET /api/v1/compliance/gaps | The open compliance gaps |
GET /api/v1/compliance/next-task | The next recommended task |
GET /api/v1/compliance/next-deadline | The next regulatory deadline |
GET /api/v1/compliance/mappings | The CRA requirement mappings |
GET /api/v1/compliance/assessments | Product assessments |
GET /api/v1/compliance/assessments/oscal | Assessment results in OSCAL format |
GET /api/v1/vulnerabilities/{id}/article14 | The Article 14 status of one report. See Article 14 Status API. |
GET /api/v1/vulnerabilities/export | Up to 100 reports as JSON |
All responses are JSON, except where the table says otherwise.
Limits
The API has no endpoint for SLA performance metrics or for the audit log alone. The full data export includes the audit log. See Data Export & Retention.