Inconsistent API response structure across backend endpoints

[A69SHUBHAM]

Problem

The backend currently returns API responses in inconsistent formats across different endpoints.

This leads to:

• Difficulty handling responses on the frontend
• Lack of a predictable structure for success and error cases
• Increased complexity in debugging and maintenance

Expected Behavior

• All API responses should follow a consistent structure
• Both success and error responses should be standardized

Proposed Solution

Introduce a unified response format:

Success response:
{
"status": "success",
"message": "Request successful",
"data": {...}
}

Error response:
{
"status": "error",
"message": "Something went wrong",
"error": {...}
}

Implementation steps:

• Create helper functions for success and error responses
• Refactor all backend endpoints to use these helpers
• Ensure proper HTTP status codes are returned
• Update frontend to handle the new response structure

Impact

• Improves consistency and maintainability
• Simplifies frontend integration
• Makes debugging and error handling easier

Additional Context

I would like to work on this issue and submit a PR.