Public REST API: Bypass restrictions, download attachments, and more

Bypass field data restrictions when creating models and findings

You can now create models and findings via the public API using legacy values that may not currently be valid. A new boolean parameter, strict_custom_field_validation, controls whether custom fields are validated strictly for both findings and inventory models.

This change provides more flexibility when importing or managing legacy data.

POST /models

POST /models/{inventory_model_cuid}/findings/{finding_type_cuid}

Download attachments

You can now download attachments using a new public /vm/api/v1/assets endpoint.

GET /assets/{key}

Reporting support

Two new public API endpoints are available for accessing reporting data:

• GET /vm/api/v1/reporting/datasets lets you list available datasets.
• GET /vm/api/v1/reporting/datasets/{id}/data allows you to retrieve raw dataset data.

Additionally, the analytics query builder now includes additional methods for accessing raw data.

GET /reporting/datasets

GET /reporting/datasets/{dataset_id}/data

Regenerate your own API keys

Regenerate your own API keys directly from your profile page. If key expiration policies are in place, you will also see how many days remain until your keys expire.

Previously, this functionality was available only to admin users.

Regenerate API keys

Return all custom finding fields in public API

The public API for model findings now returns all custom finding fields in its responses. Prior to this update, custom fields were missing from the response data.

GET /findings/{finding_type_cuid}

Add finding status

The public API has been updated to allow the creation of findings with initial statuses. Additionally, you can now use an optional field, status_cuid, in the model findings endpoint in the API.

POST /models/{inventory_model_cuid}/findings/{finding_type_cuid}

Bug fixes

Return all custom finding fields in public API

The public API for model findings now returns all custom finding fields in its responses. Prior to this update, custom fields were missing from the response data.

GET /findings/{finding_type_cuid}