Standardize API Response Format Across All Backend Endpoints#51
Open
androemeda wants to merge 1 commit intovirtualcell:mainfrom
Open
Standardize API Response Format Across All Backend Endpoints#51androemeda wants to merge 1 commit intovirtualcell:mainfrom
androemeda wants to merge 1 commit intovirtualcell:mainfrom
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This PR introduces a standardized API response format across all backend endpoints to improve consistency, debugging, and frontend integration. All responses now follow a uniform structure that includes a success flag, timestamp, optional message, and metadata when relevant.
Implementation
ResponseFormatter Utility
ResponseFormatterutility with:success_response()error_response()Controller Updates
Error Handling
Backward Compatibility
ChatBoxcomponent to support both old and new response formats during the transition phase.Response Format
Before (Inconsistent formats)
After (Standardized format)
Success Response
{ "success": true, "data": {...}, "message": "Request completed successfully", "timestamp": "2026-03-12T10:30:45.123Z", "meta": { "bmkeys": [...] } // Included only when relevant }Error Response
{ "success": false, "data": null, "message": "Failed to fetch biomodels from VCell API", "timestamp": "2026-03-12T10:30:45.123Z" }Testing
ChatBoxcomponent works with the new response structure.