API documentation
A vulnerability management API for findings, assets, and remediation workflows
The Artemes AI API exposes the same contextual findings and operational state used by the dashboard. Security engineering teams can query prioritized risk, inspect affected assets, coordinate remediation, and build reporting or automation without scraping the user interface.
JSON endpoints for findings, assets, remediations, and reporting
Reads that enforce customer context for operational security workflows
Authenticated actions for status, assignment, and due date changes
Read APIs
Query the evidence behind security posture
Use endpoints that enforce customer context to retrieve the records needed for dashboards, investigations, and automation.
Findings
List canonical findings with severity, status, exploitability signals, affected assets, ownership, and remediation context.
Assets
Retrieve device identity, operating system, scan recency, risk summaries, and finding counts for monitored infrastructure.
Context and health
Inspect context analysis decisions, reference data health, collector state, and the freshness of supporting evidence.
Workflow APIs
Move findings through an accountable remediation lifecycle
Authenticated actions update canonical state and preserve the operational record used by the dashboard.
Status decisions
Move findings through open, in progress, fixed, accepted risk, false positive, and suppression workflows.
Assignment and due dates
Set ownership and review deadlines so urgent work remains visible and exceptions do not become permanent by accident.
Schedules and reports
Create report schedules, manage delivery state, and run reports for recurring customer and governance workflows.
Integration guidance
Build automation that remains safe and explainable
Treat contextual security decisions as governed operational changes, not just API calls.
Authenticate every privileged action
Use authenticated credentials and authorization tied to the selected customer for data or changes that require server access.
Keep identifiers stable
Store canonical finding, asset, customer, and schedule identifiers instead of matching on display labels.
Handle failure explicitly
Validate response status, preserve request context, and make automated changes idempotent where the workflow permits.
Example requests
Start with focused reads for one customer
GET /api/dev/findings?customerId=300&status=activeGET /api/dev/assets?customerId=300GET /api/dev/dashboard?customerId=300Build against the Artemes AI API
Request early access to discuss authentication, customer scoping, available endpoints, and your first automation use case.
Request Early Access