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

Get deviceTypes front_image and rear_image from the API #10649

New Issue
Closed
opened 2025-12-29 21:34:10 +01:00 by adam · 3 comments
adam commented 2025-12-29 21:34:10 +01:00
Owner
Copy Link

Originally created by @Janl1 on GitHub (Jan 15, 2025).

Originally assigned to: @DanSheps on GitHub.

NetBox version

v4.2.1

Feature type

New functionality

Triage priority

N/A

Proposed functionality

Currently, I cannot retrieve the stored front_image and rear_image of a device type from the API. The API response from GET /api/dcim/device-types/ returns the URLs which are only accessible with a valid Netbox session but not with the API credentials.

If there isn't already a way to get the images with the API key, it would be nice to be able to do so.

Use case

Currently, providing the front_image and rear_image in the API response is a dead end, as it cannot be used. For a deeper integration into other systems it would be nice to be able to retrieve the stored images with a API token.

Database changes

No response

External dependencies

No response

Originally created by @Janl1 on GitHub (Jan 15, 2025). Originally assigned to: @DanSheps on GitHub. ### NetBox version v4.2.1 ### Feature type New functionality ### Triage priority N/A ### Proposed functionality Currently, I cannot retrieve the stored front_image and rear_image of a device type from the API. The API response from `GET /api/dcim/device-types/` returns the URLs which are only accessible with a valid Netbox session but not with the API credentials. If there isn't already a way to get the images with the API key, it would be nice to be able to do so. ### Use case Currently, providing the front_image and rear_image in the API response is a dead end, as it cannot be used. For a deeper integration into other systems it would be nice to be able to retrieve the stored images with a API token. ### Database changes _No response_ ### External dependencies _No response_
adam added the type: featurestatus: blockedcomplexity: medium labels 2025-12-29 21:34:10 +01:00
adam closed this issue 2025-12-29 21:34:10 +01:00
adam commented 2025-12-29 21:34:10 +01:00
Author
Owner
Copy Link

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

Access to uploaded media such as front/rear images for device types is controlled via the MediaView class, which currently supports only UI authentication. I'm not quite sure what the ideal solution here would look like, but it probably involves introducing a new REST API endpoint analogous to MediaView.

@jeremystretch commented on GitHub (Feb 20, 2025): Access to uploaded media such as front/rear images for device types is controlled via the MediaView class, which currently supports only UI authentication. I'm not quite sure what the ideal solution here would look like, but it probably involves introducing a new REST API endpoint analogous to MediaView.
adam commented 2025-12-29 21:34:10 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Aug 7, 2025):

Related to #19669

@jeremystretch commented on GitHub (Aug 7, 2025): Related to #19669
adam commented 2025-12-29 21:34:11 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Aug 7, 2025):

Marking this as blocked by #19669 for now as the solution for that will likely solve for this FR as well.

@jeremystretch commented on GitHub (Aug 7, 2025): Marking this as blocked by #19669 for now as the solution for that will likely solve for this FR as well.
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 status: blocked 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#10649
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?