Return all CablePaths which traverse a given pass-through port in NetBox
A documented NetBox operation that only reads, so it can watch for changes without altering anything. Describe what you want to happen and HumDay builds it.
What this operation does
Return all CablePaths which traverse a given pass-through port.
- GETReads data · circuits
demo.netbox.dev/circuits/circuit-terminations/{id}/paths/
How HumDay uses it
- You describe the outcome. Not this operation by name — what you want to happen. HumDay works out which operations it needs.
- The contract names it. Before anything is built, you see exactly which NetBox operations the program may use, and this is one of them.
- You approve access. Read-only access is still yours to grant, and still limited to what the contract needs.
Other NetBox operations
- Non-authenticated REST API endpoint viaPOST · changes data
- Run a Report identified as "POST · changes data
- Return the UserConfig for the currently authenticated UserGET · reads data
- Retrieve a list of job resultsGET · reads data
- Read-only list of ContentTypesGET · reads data
- This endpoint allows a userGET · reads data
- Retrieve a list of recent changesGET · reads data
- A lightweight read-only endpointGET · reads data
Questions
- Can HumDay return all cablepaths which traverse a given pass-through port in NetBox?
- Yes. This operation is published in NetBox's own API description, so HumDay can use it without a hand-built connector — once you have approved it for your automation.
- Does this change anything in my NetBox account?
- No. This is a read-only operation, so it can be used to watch for changes or fetch data without altering anything in NetBox.
- Do I need to write code?
- No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a proof run before anything touches your NetBox account.
Where this came from
Read from a published API description for NetBox at demo.netbox.dev/api/docs/?format=openapi. The description above is the provider’s own wording, not ours. Last published 2023-03-21.