PK/ID serialized for vlan/prefix/ip address status api and documentation #1278

Closed
opened 2025-12-29 16:31:01 +01:00 by adam · 0 comments
Owner

Originally created by @dirtycajunrice on GitHub (Oct 4, 2017).

Issue type

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

Description

When making scripted API calls, status requires a PK value. Although this field is not user customisable, there is no intelligent way of retrieving all of the serialized number / label options currently via API or GUI. I propose an addition to each API module allowing a query of these id/label pairs.

With the API documentation (swagger) all examples show string as an option for all types of requests. I propose a change to pk or id for the appropriate fields

Originally created by @dirtycajunrice on GitHub (Oct 4, 2017). ### Issue type [x] Feature request <!-- Requesting the implementation of a new feature --> [ ] Bug report <!-- Reporting unexpected or erroneous behavior --> [x] Documentation <!-- Proposing a modification to the documentation --> ### Description When making scripted API calls, status requires a PK value. Although this field is not user customisable, there is no intelligent way of retrieving all of the serialized number / label options currently via API or GUI. I propose an addition to each API module allowing a query of these id/label pairs. With the API documentation (swagger) all examples show string as an option for all types of requests. I propose a change to pk or id for the appropriate fields
adam added the type: feature label 2025-12-29 16:31:01 +01:00
adam closed this issue 2025-12-29 16:31:01 +01:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#1278