OPTIONS API call is missing schemas and returns wrong ones. #8189

Closed
opened 2025-12-29 20:33:36 +01:00 by adam · 2 comments
Owner

Originally created by @CADbloke on GitHub (Jun 13, 2023).

NetBox version

3.5.3

Python version

3.8

Steps to Reproduce

  1. using Postman call OPTIONS to https://demo.netbox.dev/api/dcim/devices/
  2. it only returns identical schemas for PUT & POST, both if which are actually GET schemas.
  3. similar happens for https://demo.netbox.dev/api/ipam/ip-addresses/. I assume it is the same for all endpoints.

Expected Behavior

I expected to see all available schemas for that endpoint.

I expected the POST schema to look like the docs at https://demo.netbox.dev/api/schema/swagger-ui/#/dcim/dcim_devices_create. Nested Object schemas were not ID integers, they were actual nested objects. I was hoping to use it to validate POST calls before sending them.

Observed Behavior

Missing Schemas, wrong schemas.

Originally created by @CADbloke on GitHub (Jun 13, 2023). ### NetBox version 3.5.3 ### Python version 3.8 ### Steps to Reproduce 1. using Postman call `OPTIONS` to https://demo.netbox.dev/api/dcim/devices/ 2. it only returns identical schemas for `PUT` & `POST`, both if which are actually `GET` schemas. 3. similar happens for https://demo.netbox.dev/api/ipam/ip-addresses/. I assume it is the same for all endpoints. ### Expected Behavior I expected to see all available schemas for that endpoint. I expected the `POST` schema to look like the docs at https://demo.netbox.dev/api/schema/swagger-ui/#/dcim/dcim_devices_create. Nested Object schemas were not ID integers, they were actual nested objects. I was hoping to use it to validate `POST` calls before sending them. ### Observed Behavior Missing Schemas, wrong schemas.
adam added the type: bugstatus: needs ownerpending closureseverity: low labels 2025-12-29 20:33:36 +01:00
adam closed this issue 2025-12-29 20:33:36 +01:00
Author
Owner

@github-actions[bot] commented on GitHub (Sep 22, 2023):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Do not attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our contributing guide.

@github-actions[bot] commented on GitHub (Sep 22, 2023): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. **Do not** attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our [contributing guide](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md).
Author
Owner

@github-actions[bot] commented on GitHub (Oct 22, 2023):

This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.

@github-actions[bot] commented on GitHub (Oct 22, 2023): This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#8189