@RequestBody for JSON input in Spring Boot - Step-by-Step Execution

Concept Flow - @RequestBody for JSON input

Client sends HTTP POST with JSON body

↓

Spring Boot Controller receives request

↓

@RequestBody annotation tells Spring to parse JSON

↓

Spring converts JSON to Java object

↓

Controller method uses Java object

↓

Controller returns response

This flow shows how Spring Boot uses @RequestBody to convert incoming JSON into a Java object for the controller to use.

Execution Sample

Spring Boot

record User(String name, int age) {}

@PostMapping("/users")
public String addUser(@RequestBody User user) {
    return "User " + user.name() + " added";
}

This code receives JSON with name and age, converts it to a User object, and returns a confirmation string.

Execution Table

Step	Action	Input/Condition	Result	Notes
1	Receive HTTP POST	Body: {"name":"Alice","age":30}	Request received	Client sends JSON data
2	Spring reads @RequestBody	Annotation present	Triggers JSON parsing	Spring knows to parse body as JSON
3	Parse JSON	{"name":"Alice","age":30}	Create User(name="Alice", age=30)	JSON converted to Java record
4	Call addUser method	User object with name=Alice, age=30	Method executes	User object passed as parameter
5	Return response	String "User Alice added"	Response sent to client	Confirmation message returned
6	End	No more steps	Request complete	Process finished

💡 Request handled fully; JSON parsed and method executed

Variable Tracker

Variable	Start	After Step 3	After Step 4	Final
user	null	User(name="Alice", age=30)	User(name="Alice", age=30)	User(name="Alice", age=30)

Key Moments - 3 Insights

Why does Spring need the @RequestBody annotation?

Because @RequestBody tells Spring to convert the incoming JSON into a Java object. Without it, Spring treats the body as plain text or ignores it. See execution_table step 2.

What happens if the JSON keys don't match the Java object's fields?

Spring will fail to map those fields correctly, possibly throwing an error or setting fields to default values. This is because JSON keys must match Java property names for conversion (step 3).

Can the controller method use the Java object directly after @RequestBody?

Yes, after Spring converts JSON to the Java object, the method receives it ready to use, as shown in step 4.

Visual Quiz - 3 Questions

Look at the execution_table, what is the value of 'user' after step 3?

A JSON string

B null

C User(name="Alice", age=30)

D Empty object

💡 Hint

Check variable_tracker after Step 3 for 'user' value.

At which step does Spring convert JSON into a Java object?

A Step 1

B Step 3

C Step 2

D Step 4

💡 Hint

Look at execution_table action describing JSON parsing.

If the @RequestBody annotation is removed, what changes in the execution?

A Spring treats the body as plain text, no conversion

B Spring still converts JSON automatically

C The method receives a Java object anyway

D The server throws an error immediately

💡 Hint

Refer to key_moments about the role of @RequestBody (step 2).

Concept Snapshot

@RequestBody annotation in Spring Boot
- Used on controller method parameters
- Converts incoming JSON request body into Java object
- Requires matching JSON keys and Java fields
- Enables easy use of JSON data in Java methods
- Without it, body is not parsed as JSON

Full Transcript

This visual execution shows how Spring Boot uses the @RequestBody annotation to handle JSON input. When a client sends a POST request with JSON data, Spring sees the @RequestBody annotation on the controller method parameter. This tells Spring to parse the JSON body and convert it into a Java object matching the parameter type. The example uses a User record with name and age fields. The JSON keys must match these fields for correct mapping. After conversion, the controller method receives the User object and can use it directly. The method then returns a confirmation string. If @RequestBody is missing, Spring does not parse the JSON and treats the body as plain text. This flow helps beginners understand how JSON input is handled step-by-step in Spring Boot controllers.