api request for trace produce error 404 for front or rear ports #8253

New Issue

adam · 2025-12-29T20:34:21+01:00

adam commented

2025-12-29 20:34:21 +01:00

Originally created by @hvdort on GitHub (Jun 27, 2023).

NetBox version

v3.5.4

Python version

3.8

Steps to Reproduce

Requesting the cable trace using de GUI works fine. For interfaces as well as for front-ports and rear-ports. However, the REST-API seems to be only support the trace starting by an interface. If I request the trace starting from an front- or rear-port, I receive error 404.

working url's:
/dcim/interfaces/{id}/trace/
/dcim/front-ports/{id}/trace/
/dcim/rear-ports/{id}/trace/

and also working:
/api/dcim/interfaces/{id}/trace/

but not working url's:
/api/dcim/front_ports/{id}/trace/
/api/dcim/rear_ports/{id}/trace/

Expected Behavior

implementing trace option also using the API.

Observed Behavior

error 404 (not found)

Originally created by @hvdort on GitHub (Jun 27, 2023). ### NetBox version v3.5.4 ### Python version 3.8 ### Steps to Reproduce Requesting the cable trace using de GUI works fine. For interfaces as well as for front-ports and rear-ports. However, the REST-API seems to be only support the trace starting by an interface. If I request the trace starting from an front- or rear-port, I receive error 404. working url's: /dcim/interfaces/{id}/trace/ /dcim/front-ports/{id}/trace/ /dcim/rear-ports/{id}/trace/ and also working: /api/dcim/interfaces/{id}/trace/ but not working url's: /api/dcim/front_ports/{id}/trace/ /api/dcim/rear_ports/{id}/trace/ ### Expected Behavior implementing trace option also using the API. ### Observed Behavior error 404 (not found)

adam closed this issue

2025-12-29 20:34:21 +01:00

adam commented

2025-12-29 20:34:22 +01:00

@kkthxbye-code commented on GitHub (Jun 27, 2023):

Hi, this is not a bug an intended. If you want to change the functionality, you need to create a feature request. The way it works currently is that rear and front ports implement the /paths endpoint which essentially will return all CablePaths that run through the port.

@kkthxbye-code commented on GitHub (Jun 27, 2023): Hi, this is not a bug an intended. If you want to change the functionality, you need to create a feature request. The way it works currently is that rear and front ports implement the `/paths` endpoint which essentially will return all CablePaths that run through the port.

adam commented

2025-12-29 20:34:22 +01:00

@hvdort commented on GitHub (Jun 27, 2023):

Sorry, I hadn't discovered that option yet...

@hvdort commented on GitHub (Jun 27, 2023): Sorry, I hadn't discovered that option yet...

Sign in to join this conversation.

Branches Tags

main

update-changelog-comments-docs

feature-removal-issue-type

20911-dropdown

20239-plugin-menu-classes-mutable-state

21097-graphql-id-lookups

feature

fix_module_substitution

20923-dcim-templates

20044-elevation-stuck-lightmode

feature-ip-prefix-link

v4.5-beta1-release

20068-import-moduletype-attrs

20766-fix-german-translation-code-literals

20378-del-script

7604-filter-modifiers-v3

circuit-swap

12318-case-insensitive-uniqueness

20637-improve-device-q-filter

20660-script-load

19724-graphql

20614-update-ruff

14884-script

02496-max-page

19720-macaddress-interface-generic-relation

19408-circuit-terminations-export-templates

20203-openapi-check

fix-19669-api-image-download

7604-filter-modifiers

19275-fixes-interface-bulk-edit

fix-17794-get_field_value_return_list

11507-show-aggregate-and-rir-on-api

9583-add_column_specific_search_field_to_tables

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/netbox#8253