Skip to content

[BACKEND] Add request IDs to structured validation and server error payloads consistently #568

@utksh1

Description

@utksh1

Summary

Request IDs are useful only if clients can correlate them with failures. SecuScan should make that correlation obvious in error payloads as well as headers.

Scope

  • Decide where request IDs belong in structured error responses.
  • Apply the contract consistently across validation errors and server errors.
  • Add regression tests for the chosen shape.

Acceptance criteria

  • Error payloads follow a documented request ID contract.
  • Validation and server errors behave consistently.
  • Tests cover the chosen response shape.

Metadata

Metadata

Assignees

Labels

area:backendBackend API, database, or service worklevel:advanced55 pts difficulty label for advanced contributor PRspriority:mediumImportant issue with normal urgencytype:featureFeature work category bonus label

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions