Skip to content

feat: standardize API error responses across all endpoints - #138

Open
DavisVT wants to merge 2 commits into
Core-Foundry:mainfrom
DavisVT:feature/standardize-api-error-responses
Open

feat: standardize API error responses across all endpoints#138
DavisVT wants to merge 2 commits into
Core-Foundry:mainfrom
DavisVT:feature/standardize-api-error-responses

Conversation

@DavisVT

@DavisVT DavisVT commented Jul 30, 2026

Copy link
Copy Markdown
Contributor
  • Add ApiErrorResponse interface and buildErrorResponse helper
  • Update all 6 API endpoints to use standardized error format with error codes
  • Add error codes: INVALID_FORM_DATA, INVALID_JSON, INVALID_PAYLOAD, FILE_VALIDATION_FAILED, TASK_CREATION_FAILED, TASK_NOT_FOUND, SUBMISSION_FAILED, STATS_FETCH_FAILED, HEALTH_CHECK_FAILED, RATE_LIMIT_EXCEEDED
  • Update rate limiting to use standardized error response
  • Add comprehensive tests for api-response module
  • Update TASK_API.md documentation with error codes and format

closes #52

DavisVT and others added 2 commits July 30, 2026 03:09
- Add ApiErrorResponse interface and buildErrorResponse helper
- Update all 6 API endpoints to use standardized error format with error codes
- Add error codes: INVALID_FORM_DATA, INVALID_JSON, INVALID_PAYLOAD, FILE_VALIDATION_FAILED, TASK_CREATION_FAILED, TASK_NOT_FOUND, SUBMISSION_FAILED, STATS_FETCH_FAILED, HEALTH_CHECK_FAILED, RATE_LIMIT_EXCEEDED
- Update rate limiting to use standardized error response
- Add comprehensive tests for api-response module
- Update TASK_API.md documentation with error codes and format
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

enhancement: standardize API error responses

2 participants