Interface's VLAN relationship(s) not exposed via API #1701

Closed
opened 2025-12-29 16:34:32 +01:00 by adam · 1 comment
Owner

Originally created by @pm17788 on GitHub (Apr 26, 2018).

Issue type

[ ] Feature request
[x] Bug report
[ ] Documentation

Environment

  • Python version: 3.5.2
  • NetBox version: 2.3.2

Description

Once an Interface is set to have the 802.1Q attribute, it is possible to use the WebUI to add VLAN(s) to it.
However, there does not appear to be a way to see VLAN <=> Interface memberships via the API.
neither /virtualization/interfaces/, /dcim/interfaces/, nor /ipam/vlans/ seem to return data indicating that a particular interface has any VLAN information associated with it at all.

Originally created by @pm17788 on GitHub (Apr 26, 2018). ### Issue type [ ] Feature request [x] Bug report [ ] Documentation ### Environment * Python version: 3.5.2 * NetBox version: 2.3.2 ### Description Once an Interface is set to have the 802.1Q attribute, it is possible to use the WebUI to add VLAN(s) to it. However, there does not appear to be a way to see VLAN <=> Interface memberships via the API. neither `/virtualization/interfaces/`, `/dcim/interfaces/`, nor `/ipam/vlans/` seem to return data indicating that a particular interface has any VLAN information associated with it at all.
adam closed this issue 2025-12-29 16:34:33 +01:00
Author
Owner

@pm17788 commented on GitHub (May 10, 2018):

D'Oh! Missed the data structures right under my nose. Sorry about that.

@pm17788 commented on GitHub (May 10, 2018): D'Oh! Missed the data structures right under my nose. Sorry about that.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#1701