starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-11 21:10:29 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

Expose tagged objects through REST api #10377

New Issue
Closed
opened 2025-12-29 21:30:38 +01:00 by adam · 2 comments
adam commented 2025-12-29 21:30:38 +01:00
Owner
Copy Link

Originally created by @LachTrip on GitHub (Oct 17, 2024).

Originally assigned to: @jeremystretch on GitHub.

NetBox version

v4.1.1

Feature type

Data model extension

Triage priority

This is a very minor change

Proposed functionality

Add a new endpoint to get the list of the objects using a specific tag.

Use case

Looking up objects by their tags through the api currently requires numerous api calls to search through all object types. The underlying functionality exists as demonstrated by visiting the tag's display_url and looking under "Tagged Objects".

Database changes

N/A

External dependencies

N/A

Originally created by @LachTrip on GitHub (Oct 17, 2024). Originally assigned to: @jeremystretch on GitHub. ### NetBox version v4.1.1 ### Feature type Data model extension ### Triage priority This is a very minor change ### Proposed functionality Add a new endpoint to get the list of the objects using a specific tag. ### Use case Looking up objects by their tags through the api currently requires numerous api calls to search through all object types. The underlying functionality exists as demonstrated by visiting the tag's display_url and looking under "Tagged Objects". ### Database changes N/A ### External dependencies N/A
adam added the status: acceptedtype: featurecomplexity: mediumnetbox labels 2025-12-29 21:30:38 +01:00
adam closed this issue 2025-12-29 21:30:38 +01:00
adam commented 2025-12-29 21:30:38 +01:00
Author
Owner
Copy Link

@davekempe commented on GitHub (Oct 22, 2024):

This would be useful for us, as we can then easily hit the API to get a list of objects to work with. This enhances Netbox as a SoT - allowing other tools to easily get the 'next' list of things to work on.

@davekempe commented on GitHub (Oct 22, 2024): This would be useful for us, as we can then easily hit the API to get a list of objects to work with. This enhances Netbox as a SoT - allowing other tools to easily get the 'next' list of things to work on.
adam commented 2025-12-29 21:30:39 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Feb 6, 2025):

This would probably manifest as a /api/extras/tagged-objects/ REST API endpoint (or similar).

@jeremystretch commented on GitHub (Feb 6, 2025): This would probably manifest as a `/api/extras/tagged-objects/` REST API endpoint (or similar).
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
beta
breaking change
complexity: high
complexity: low
complexity: medium
needs milestone
netbox
pending closure
plugin candidate
pull-request
Mirrored from GitHub Pull Request
 severity: high
severity: low
severity: medium
status: accepted
status: backlog
status: blocked
status: duplicate
status: needs owner
status: needs triage
status: revisions needed
status: under review
topic: GraphQL
topic: Internationalization
topic: OpenAPI
topic: UI/UX
topic: cabling
topic: event rules
topic: htmx navigation
topic: industrialization
topic: migrations
topic: plugins
topic: scripts
topic: templating
topic: testing
type: bug
type: deprecation
type: documentation
type: feature
type: housekeeping
type: translation
No Label complexity: medium netbox status: accepted type: feature
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#10377
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?