GET /discovery/{id}/network-device API arguments

The attached image below shows the GET /discovery/{id}/network-device API. It is documented as taking an id, which is the id of the discovery job.

The second attached image below shows the argument fields for the API. That seems to imply that the API takes a taskId and a discovery id. That is probably so that one can see which devices were discovered for a given invocation of the discovery job. That is potentially quite useful, but it is not clear, from the documentation, how that would actually work. Specifically, where does the taskId go. It is not documented as appearing in the URL, and, as this is a GET, there is no body.

Typically these parameters are passed as query args to the URL.  If you open your browser's developer console and look at the network tab you should see exactly how the API is called.  taskId may be passed after the '?'.

The idea of using the developer tools in the browser is a good one. Suspect that this API form is being used, then, in web UI when one gets the devices for the results of a specific discovery invocation.

if you fill in SOME value and hit "Try it out" you'll see how the request is sent to the server in the developer console (Network tab).  That will show how you can make that call from scripts or Postman. Also, the "Parameter Type" column tells you if it is a path or query parameter.