How do you implement global API error handling with @ControllerAdvice and ProblemDetail?

Maps known framework and application failures to RFC 9457 responses while preserving stable codes, safe detail, and correlation.

1Say itAnswer out loud first

2CompareCompare with Core answer

3RefineRefine with Stronger and Advanced

TL;DR

A @RestControllerAdvice can declare @ExceptionHandler methods that apply across REST controllers. Handlers map known exceptions to a status and a stable response, and Spring can render ProblemDetail or ErrorResponse using the RFC 9457 media type. I include a machine-readable type or code, a safe title and detail, the instance path where useful, and a correlation identifier. Validation errors add structured field or parameter entries.

Full answer below

Practice focus

Exception resolution, handler specificity, Problem Details, validation rendering, information disclosure, and contract stability.

Answer first

Answer path

Core answer first, then checkpoints toward a stronger answer.

Start
Core answer
Start here. This is the direct spoken answer to practice first.
Overview
Global advice centralizes HTTP rendering; it does not replace meaningful exceptions or domain outcome design.
A @RestControllerAdvice can declare @ExceptionHandler methods that apply across REST controllers. Handlers map known exceptions to a status and a stable response, and Spring can render ProblemDetail or ErrorResponse using the RFC 9457 media type. I include a machine-readable type or code, a safe title and detail, the instance path where useful, and a correlation identifier. Validation errors add structured field or parameter entries.
Checkpoint
Stronger answer
Optional upgrade with examples, trade-offs, and sharper phrasing.

Review signals

Use these to catch weak phrasing, shallow reasoning, and risky claims.

Common mistakesCandidateCommon mistakesMistakes that weaken the answer or signal shallow understanding.Open details

Details

Returning exception messages directly to clients.
Catching Exception in every controller.
Treating every business failure as status 500.

How do you implement global API error handling with @ControllerAdvice and ProblemDetail?

Practice focus

Answer path

Overview

Review signals

Follow-up prompts

Continue the section

Tech stacks

Skill areas

Suggest an improvement

Found this answer useful?