@PostMapping for POST requests in Spring Boot - Step-by-Step Execution

Concept Flow - @PostMapping for POST requests

Client sends POST request

↓

Spring Boot matches URL

↓

@PostMapping method invoked

↓

Method processes data

↓

Method returns response

↓

Response sent back to client

This flow shows how a POST request from a client is handled by a Spring Boot controller method annotated with @PostMapping.

Execution Sample

Spring Boot

@PostMapping("/submit")
public String submitData(@RequestBody Data data) {
    return "Received: " + data.getName();
}

This method handles POST requests to '/submit', reads JSON data into a Data object, and returns a confirmation string.

Execution Table

Step	Action	Input/Condition	Result	Output
1	Client sends POST request	POST /submit with JSON {"name":"Alice"}	Request received by server	No output yet
2	Spring Boot matches URL	URL '/submit' matches @PostMapping('/submit')	Controller method selected	No output yet
3	Deserialize JSON	JSON body {"name":"Alice"}	Data object created with name='Alice'	No output yet
4	Invoke method	submitData(data)	Method runs with data.name='Alice'	No output yet
5	Return response	Return string 'Received: Alice'	Response body set	Response sent: 'Received: Alice'
6	Client receives response	Response 'Received: Alice'	Client processes response	Displayed or used by client

💡 Request handled fully; response sent back to client.

Variable Tracker

Variable	Start	After Step 3	After Step 4	Final
data	null	Data{name='Alice'}	Data{name='Alice'}	Data{name='Alice'}
returnValue	null	null	"Received: Alice"	"Received: Alice"

Key Moments - 2 Insights

Why does the method parameter have @RequestBody?

Because the JSON data sent in the POST request body needs to be converted into a Java object. @RequestBody tells Spring Boot to do this conversion automatically, as shown in execution_table step 3.

What happens if the URL does not match @PostMapping path?

Spring Boot will not invoke this method. Instead, it will look for another matching handler or return a 404 error. This is shown in execution_table step 2 where URL matching happens.

Visual Quiz - 3 Questions

Look at the execution table, what is the value of 'data' after step 3?

A null

B "Received: Alice"

C Data{name='Alice'}

D Empty object

💡 Hint

Check the 'variable_tracker' table under 'After Step 3' for 'data'.

At which step does the method return the response string?

A Step 2

B Step 5

C Step 3

D Step 6

💡 Hint

Look at the 'execution_table' row where 'Return response' happens.

If the client sends a GET request instead of POST, what happens?

A Spring Boot returns 404 Not Found

B The @PostMapping method runs anyway

C The JSON is deserialized but method not called

D The server crashes

💡 Hint

Refer to key_moments about URL and method matching in execution_table step 2.

Concept Snapshot

@PostMapping maps HTTP POST requests to a method.
Use @RequestBody to get JSON data as a Java object.
Method processes data and returns a response.
Spring Boot matches URL and HTTP method before calling.
Response is sent back to client after method returns.

Full Transcript

When a client sends a POST request to a Spring Boot server, the server looks for a method annotated with @PostMapping that matches the request URL. The JSON data sent in the request body is automatically converted into a Java object if the method parameter has @RequestBody. The method runs with this data, processes it, and returns a response string. This response is sent back to the client. If the URL or HTTP method does not match, the request is not handled by this method and may result in an error.

Practice

1. What is the main purpose of the @PostMapping annotation in Spring Boot?

easy

A. To map HTTP PUT requests to a specific method

B. To map HTTP POST requests to a specific method

C. To map HTTP DELETE requests to a specific method

D. To map HTTP GET requests to a specific method

Solution

1. Step 1: Understand HTTP methods

   HTTP POST is used to send data to the server, so a method handling POST requests must be mapped accordingly.

2. Step 2: Role of @PostMapping

   @PostMapping specifically maps HTTP POST requests to a method in a Spring Boot controller.

3. Final Answer:

   To map HTTP POST requests to a specific method -> Option B

4. Quick Check:

   @PostMapping = POST request handler [OK]

Hint: POST requests use @PostMapping to connect URL and method [OK]

Common Mistakes:

• Confusing @PostMapping with @GetMapping
• Using @PostMapping for GET requests
• Not understanding HTTP method differences

2. Which of the following is the correct syntax to create a POST endpoint in Spring Boot that accepts JSON data?

easy

A. @PostMapping("/submit")
public String submitData(String data) { return "Received"; }

B. @GetMapping("/submit")
public String submitData(@RequestBody String data) { return "Received"; }

C. @PostMapping("/submit")
public String submitData(@RequestBody String data) { return "Received"; }

D. @PostMapping("/submit")
public String submitData(@RequestParam String data) { return "Received"; }

Solution

1. Step 1: Identify correct annotation and parameter

   The method must use @PostMapping to handle POST requests and @RequestBody to receive JSON data from the request body.

2. Step 2: Check each option

   @PostMapping("/submit") public String submitData(@RequestBody String data) { return "Received"; } uses @PostMapping and @RequestBody correctly. @GetMapping("/submit") public String submitData(@RequestBody String data) { return "Received"; } uses @GetMapping which is wrong. @PostMapping("/submit") public String submitData(String data) { return "Received"; } misses @RequestBody, so data won't be parsed from JSON. @PostMapping("/submit") public String submitData(@RequestParam String data) { return "Received"; } uses @RequestParam which reads query parameters, not JSON body.

3. Final Answer:

   @PostMapping("/submit") public String submitData(@RequestBody String data) { return "Received"; } -> Option C

4. Quick Check:

   @PostMapping + @RequestBody = correct syntax [OK]

Hint: Use @RequestBody to get JSON data in POST method [OK]

Common Mistakes:

• Using @GetMapping instead of @PostMapping
• Forgetting @RequestBody for JSON input
• Using @RequestParam for JSON body data

3. Given the following Spring Boot controller method, what will be the output when a POST request with body "Hello" is sent to /greet? @PostMapping("/greet") public String greet(@RequestBody String name) { return "Hi, " + name + "!"; }

medium

A. "Hi, Hello!"

B. "Hello"

C. "Hi, name!"

D. HTTP 404 Not Found

Solution

1. Step 1: Understand method behavior

   The method takes the request body as a String parameter named 'name' and returns "Hi, " plus that name plus "!".

2. Step 2: Apply input to output

   Input body is "Hello", so the output will be "Hi, Hello!".

3. Final Answer:

   "Hi, Hello!" -> Option A

4. Quick Check:

   Input "Hello" returns "Hi, Hello!" [OK]

Hint: Return greeting by concatenating input string [OK]

Common Mistakes:

• Ignoring @RequestBody and expecting query param
• Confusing output with input
• Assuming endpoint is missing (404)

4. Identify the error in this Spring Boot POST method: @PostMapping("/addUser") public String addUser(String user) { return "User " + user + " added"; }

medium

A. Method return type should be void

B. Incorrect HTTP method annotation, should be @GetMapping

C. Missing @PathVariable annotation

D. Missing @RequestBody annotation for 'user' parameter

Solution

1. Step 1: Check parameter binding

   The method expects to receive data in the POST request body, so the parameter must be annotated with @RequestBody to bind JSON or raw data.

2. Step 2: Verify annotations

   Without @RequestBody, Spring won't map the request body to the 'user' parameter, causing it to be null or empty.

3. Final Answer:

   Missing @RequestBody annotation for 'user' parameter -> Option D

4. Quick Check:

   POST body needs @RequestBody on parameter [OK]

Hint: Add @RequestBody to method parameter for POST data [OK]

Common Mistakes:

• Forgetting @RequestBody on POST method parameters
• Using @GetMapping for POST endpoints
• Confusing @PathVariable with request body

5. You want to create a Spring Boot POST endpoint /register that accepts a JSON object with fields username and email, maps it to a Java record UserData(String username, String email), and returns a confirmation message. Which method signature correctly implements this?

hard

A. @PostMapping("/register")
public String registerUser(@RequestBody UserData user) {
return "User " + user.username() + " registered with email " + user.email();
}

B. @PostMapping("/register")
public String registerUser(UserData user) {
return "User " + user.username() + " registered";
}

C. @PostMapping("/register")
public String registerUser(@RequestParam UserData user) {
return "User " + user.username() + " registered";
}

D. @PostMapping("/register")
public String registerUser(@PathVariable UserData user) {
return "User " + user.username() + " registered";
}

Solution

1. Step 1: Understand data binding for POST JSON

   To map JSON request body to a Java record, the parameter must be annotated with @RequestBody.

2. Step 2: Check each option

   @PostMapping("/register") public String registerUser(@RequestBody UserData user) { return "User " + user.username() + " registered with email " + user.email(); } correctly uses @RequestBody with UserData record and accesses its fields. @PostMapping("/register") public String registerUser(UserData user) { return "User " + user.username() + " registered"; } misses @RequestBody, so mapping fails. Options C and D use @RequestParam and @PathVariable which are for query/path parameters, not JSON body.

3. Final Answer:

   @PostMapping("/register") public String registerUser(@RequestBody UserData user) { return "User " + user.username() + " registered with email " + user.email(); } -> Option A

4. Quick Check:

   @RequestBody + record parameter = correct POST JSON mapping [OK]

Hint: Use @RequestBody with record to map JSON POST data [OK]

Common Mistakes:

• Omitting @RequestBody on complex objects
• Using @RequestParam or @PathVariable for JSON body
• Not accessing record fields correctly