REST API embarrassing newbie question: deep depth breaks API call

dplaflammeIBX — Wed, 04 Jun 2025 09:59:03 GMT

I'm an old fogey learning Powershell to learn REST API to automate various storage related tasks, including managing our NetApp clusters. We've just enabled file analytics on a few volumes, having just recently gone to OnTAP 9.10.1 P3. I'm having problems with a "/storage/volumes/{volume.uuid}/files/{path}" REST API call. It works when the path only has one "/" characters indicating going into a subdirectory but fails when I try to go to a deeper level.

Since I know I'm a newbie at too many things, I figure I'm making a newbie mistake in how I'm passing the path to the API call; I'm just including it in the URI. Can anyone point out an alternate approach will help the REST API parser recognize which API call I'm making and which path I want?

works: https://(redacted)/api/storage/volumes/09f07ef6-b5da-4bdf-b478-38270997ed94/files/dss?type=directory&fields=svm,volume,path,name,type,size,analytics

fails: https://(redacted)/api/storage/volumes/09f07ef6-b5da-4bdf-b478-38270997ed94/files/dss/NiceLog?type=directory&fields=svm,volume,path,name,type,size,analytics

Error: "error": {
"message": "API not found",
"code": "3"

}

Thanks,

Nick

Re: REST API embarrassing newbie question: deep depth breaks API call

dplaflammeIBX — Thu, 07 Jul 2022 16:39:00 GMT

Never mind; I should have taken more seriously the note to replace "/" with "%2F" and "." with "%2E".

D'oh!

topic Re: REST API embarrassing newbie question: deep depth breaks API call in ONTAP Rest API Discussions

REST API embarrassing newbie question: deep depth breaks API call

Re: REST API embarrassing newbie question: deep depth breaks API call