NetBox API Related Object Filter Support Boundaries

NetBox exposes its REST API through Django REST Framework, and the DjangoFilterBackend permits double-underscore traversal into related model fields. When building client queries that filter on attributes of related objects, the exact set of supported lookup expressions—such as exact, containment, or range lookups—can be difficult to predict without inspecting a specific deployment. Because NetBox's API filter configuration and supported query patterns may shift between major releases, a filter that works on one version is not guaranteed to behave identically on another.

The practical uncertainty lies in whether a given related-field lookup is rejected at the schema level, silently ignored, or evaluated by the ORM in a way that produces unexpected results. Teams maintaining automation or integration scripts need a reliable way to determine the supported boundary for a target NetBox instance without relying on trial and error across every possible field relationship.

Which lookup expressions does the DjangoFilterBackend configuration in NetBox guarantee for related-object filters on a given major version? How can a client discover the supported related-field lookups for a specific NetBox instance before issuing production queries? Are there documented differences in related-field filter support between recent NetBox releases that affect API client compatibility?