Feature: Standardize API error response format

[Smartdevs17]

Problem

Error responses are inconsistent across endpoints. Some return { success: false, error: string }, others return different formats from the error handler middleware.

Context

API consumers must handle multiple response formats, increasing client complexity.

Proposed Solution

Define a standard error response:

interface ErrorResponse {
  success: false;
  error: {
    code: string;
    message: string;
    details?: unknown;
  };
  requestId?: string;
}

Acceptance Criteria

• All error responses follow the same schema
• Error codes defined and documented
• Error handler middleware produces standard format
• Tests verify error response structure

Technical Notes

• Files: api/src/middleware/errorHandler.ts, api/src/types/index.ts

Constraints

• Backward compatible (keep success field)

[drips-wave]

This issue has been added to the Stellar Wave Program and is worth 100 Points.

🧑‍💻 Interested in contributing? Apply to work on this issue on Drips Wave, earn points, and receive rewards.

Warning

Only applications submitted via the apply link above will be considered. Please do not apply by commenting on the issue or opening a PR directly.

🤠 Repo maintainers: You can manage this issue's Points and Complexity on your Maintainer Dashboard here. Please keep an eye on applications and respond quickly 💙

ℹ️ Learn more about Drips Wave