Description:
There is a mismatch between the documented parameters of the /dashboard endpoint and what is available in the browsable REST API.
According to the API documentation, /dashboard supports the following parameters:
organization_slug: Organization slug (e.g. PHYTunes)
location_id: Location ID
floorplan_id: Floor plan ID
time: Timeframe in days (e.g. 3d means last 3 days)
start / end: Start and end time in YYYY-MM-DD H:M:S format
However, in the browsable REST API interface, these parameters are not listed or available.
Expected behavior:
The browsable API should display and accept the same parameters described in the API documentation.
Actual behavior:
The browsable API shows no available parameters for /dashboard.
Steps to reproduce:
- Open the browsable API.
- Navigate to the
/dashboard endpoint.
- Compare available parameters with those listed in the API documentation.
Additional context:
The issue may be related to missing filterset_fields or serializer configuration for the /dashboard view.
Description:
There is a mismatch between the documented parameters of the
/dashboardendpoint and what is available in the browsable REST API.According to the API documentation,
/dashboardsupports the following parameters:organization_slug: Organization slug (e.g. PHYTunes)location_id: Location IDfloorplan_id: Floor plan IDtime: Timeframe in days (e.g.3dmeans last 3 days)start/end: Start and end time inYYYY-MM-DD H:M:SformatHowever, in the browsable REST API interface, these parameters are not listed or available.
Expected behavior:
The browsable API should display and accept the same parameters described in the API documentation.
Actual behavior:
The browsable API shows no available parameters for
/dashboard.Steps to reproduce:
/dashboardendpoint.Additional context:
The issue may be related to missing
filterset_fieldsor serializer configuration for the/dashboardview.