Group name missing from API call result

[l0l1l2l3l2l1l0l]

Hi.

When creating a custom object, group name is useful feature to group forms of a field under custom objects.

• My custom objects
• with 10 fields
• but I want to group 3, 3, 4 fields together

And this works well in netbox dashboard UI
but with API call, it does not show group name.

Can we say this is how it is design or is not yet implemented.

group name is set and visible with GUI

..

but there is no group name in each field (ip_desc and range)

{
"id": 3,
"url": "http://192.168.122.241:8000/api/plugins/custom-objects/dhcp-scopes/3/",
"display": "DHCP Scope 3",
"created": "2025-10-08T19:35:40.030588Z",
"last_updated": "2025-10-22T13:34:10.157358Z",
"tags": [],
"ip_desc": "my good dhcp ip addr",
"range": {
"id": 1,
"url": "http://192.168.122.241:8000/api/ipam/ip-ranges/1/",
"display": "1.99.99.1-10/24",
"family": {
"value": 4,
"label": "IPv4"
},
"start_address": "1.99.99.1/24",
"end_address": "1.99.99.10/24",
"description": ""
}
}

[ed-ud]

As I understand it, Custom Object Type are just regular Custom Fields... so you can query fields for the given object type with the REST API using the API endpoint /extras/custom-fields and matching the names in the "object_types" list for a given Custom Field to then extract the group name used for that field.

[ed-ud]

Clarification...

I meant to say "Custom Object Type FIELDS are just regular Custom Fields" sharing the existing framework, but that is not the case. I spent too much time looking at an alternative that would make new models via the normal mechanism that all have the same real fields and then used Custom Fields to enhance each new model separately, without dynamic model changes and migrations, etc.

Sorry for injecting confusion here.

[bctiemann]

Hi -- that's not true, the group_name field is an attribute of CustomObjectTypeField, which is a fully concrete model. It's just missing from the serializer.

[bctiemann]

PR: #274