GET /api/v1/settings/sources – Internal Server Error when invalid column name is passed in query parameters*

[sagarkumar-webkul]

API Issue Report

---

Title

GET /api/v1/settings/sources – Internal Server Error when invalid column name is passed in query parameters

---

Description

When sending a GET request to the /api/v1/settings/sources endpoint with an invalid or non-existent column name (e.g., in filters, sorting, or search), the API returns a 500 Internal Server Error.

Instead, it should return a proper validation error or a 400 Bad Request with a user-friendly message indicating that the column does not exist.

---

Steps to Reproduce

1. Send a GET request to /api/v1/settings/sources?sort=invalid_column.
2. Observe the server returns a 500 Internal Server Error.

---

Expected Behavior

The API should return a 400 Bad Request with a descriptive message such as:
"Invalid column name 'invalid_column' in sort parameter."

---

Actual Behavior

Returns a 500 Internal Server Error without a clear explanation.