I can make a link for a file, using a full path and the links API.
But I cannot get the API to give me an existing link for such a file - I'd like to re-use links rather than make new ones every time, since we use a lot of permanent links for our system manuals.
In other words, if I want to use an existing link rather than make a new one, I can’t make it work. The GET option for the API always returns ALL links, regardless of whether I use the path option or not. It returns no error, but simply returns 2,000 links which obviously are not associated with that file.
I don't want to have to go through thousands of links returned by the API to see if the right one is among them (I'd have to get a full path for each link ID, and "spin my wheels" endlessly to check)
This implies that the “Path” parameter can be used to return links for just a file or folder. I am finding that I can use the “Post” version just fine to make a link (which also makes it look like the syntax of my path is correct, because it recognizes the path there, and returns a new link), but not the GET version.
Here’s my code: This first code does not work (returns all links ever made instead of file specific ones)