Discrepancy with Public REST and private cli REST output/records for volume

[CR1988]

We are seeing inconsistent behavior between ONTAP REST APIs:

• The public REST API ("/api/storage/volumes") only returns a subset of RW data volumes.

• The private CLI REST API ("/api/private/cli/volume") correctly returns the full set.

• Additionally, the public REST API sometimes throws errors like “SVM not found” after certain records are displayed

Expected Behavior

The public REST API should return all valid volumes, excluding only system, root, or transient volumes.

Impact

• Monitoring and automation tools (e.g., NetApp Harvest) rely on the public REST API output.

• Because the API is incomplete and inconsistent, monitoring dashboards and alerts are missing critical volumes.

• This poses risk to automation workflows that assume complete and accurate API responses.

Request

Please investigate why the public REST API is returning incomplete volume data and throwing SVM errors, while the private CLI API provides the correct information.
We need guidance on whether this is a known limitation, configuration issue, or a bug in ONTAP REST.

[CR1988]

"_links": {
"self": {
"href": "/api/storage/volumes?return_records=true&fields=anti_ransomware.dry_run_start_time,anti_ransomware.state,clone.parent_snapshot.name,clone.split_estimate,is_object_store,name,snapmirror.destinations.is_cloud,snapmirror.destinations.is_ontap,snapmirror.is_protected,svm.name&is_constituent=false&max_records=500"
}
},
"error": {
"message": "SVM \"78\" does not exist. ",
"code": "2621462"
}
}

[CR1988 · Accepted solution]

Case 2010493898 opened for this issue. Both APIs output attached to the case notes