Changes to ONTAP REST API calls
Suggest changes
PDFs
NetApp continues to enhance and update the ONTAP REST API with each major product release. These updates can occasionally include changes to existing API calls, such as the parameters and default values used. These changes can affect software that accesses the REST API.
Changes to existing ONTAP REST API calls
Any changes to the existing API calls can affect software that accesses the REST API. You should review the list of changes in the table below to determine if there is an impact to your ONTAP automation environment. Each entry includes the applicable API endpoint, a description of the change, and the ONTAP release it was introduced.
| Endpoint | Description of change | ONTAP release |
|---|---|---|
|
The field _links in the response was removed from the duogroup for these endpoints. There is no recommended customer action or workaround. The field is expected to be added back in a future ONTAP release. |
9.15.1 |
ONTAP REST API reference documentation errors
As NetApp enhances and updates the ONTAP REST API, sometimes errors can be introduced in the online reference documentation. These errors can create confusion when using the API but generally don't impact or disrupt your ONTAP automation software or environment.
You should review the list of errors in the table below. This will help you better understand and navigate the ONTAP REST API reference documentation. Each entry includes the applicable API endpoint, a description of the error, and the ONTAP release it was introduced.
| Endpoint | Description of change | ONTAP release |
|---|---|---|
|
The REST API documentation for the endpoint indicates that specifier is a valid field. However, the quota specifier is not supported with this endpoint. There is no recommended customer action or workaround. |
9.6 |