Skip to content

Add a standardized error-response contract across API routes #196

@robertocarlous

Description

@robertocarlous

Why
The backend already has structured middleware and request IDs, but response bodies can still vary by route. A standardized error shape would make integrations and client handling more predictable.

Acceptance criteria

  • Define one canonical error response format.
  • Apply it consistently across auth, admin, analytics, and public routes.
  • Document the format and include examples for 400, 401, 403, 404, and 500 responses.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions