@Parameter and @Schema annotations in Spring Boot - Mini Project: Build & Apply

Using @Parameter and @Schema Annotations in Spring Boot

📖 Scenario: You are building a simple Spring Boot REST API for a bookstore. You want to document your API parameters and model properties clearly for API users using OpenAPI annotations.

🎯 Goal: Create a Spring Boot controller method with a query parameter documented using @Parameter annotation and a model class with a field documented using @Schema annotation.

📋 What You'll Learn

Create a controller method with a query parameter named author documented with @Parameter annotation

Create a model class Book with a field title documented with @Schema annotation

Use exact annotation attributes as specified

Follow Spring Boot and OpenAPI annotation syntax

💡 Why This Matters

🌍 Real World

API documentation is essential for backend services so frontend developers and API consumers understand how to use the API correctly.

💼 Career

Knowing how to use @Parameter and @Schema annotations is important for backend developers working with Spring Boot to create well-documented REST APIs.

1

Create the Book model class

Create a public class called Book with a private String field named title.

Spring Boot

public class Book {
    // Your code here
}

Hint

Define a class named Book and add a private field title of type String.

2

Add @Schema annotation to the title field

Add the @Schema(description = "Title of the book") annotation above the title field in the Book class.

Spring Boot

public class Book {
    // Add @Schema annotation here
    private String title;
}

Hint

Use @Schema from io.swagger.v3.oas.annotations.media and add the description attribute.

3

Create a controller method with a query parameter

Create a Spring Boot REST controller class named BookController with a method getBooks that accepts a query parameter author of type String.

Spring Boot

import org.springframework.web.bind.annotation.RestController;
import org.springframework.web.bind.annotation.GetMapping;
import org.springframework.web.bind.annotation.RequestParam;

@RestController
public class BookController {
    // Your code here
}

Hint

Create a controller class with a method annotated with @GetMapping("/books") and a parameter author annotated with @RequestParam.

4

Add @Parameter annotation to the author query parameter

Add the @Parameter(description = "Author name to filter books") annotation above the author parameter in the getBooks method.

Spring Boot

import io.swagger.v3.oas.annotations.Parameter;

@RestController
public class BookController {
    @GetMapping("/books")
    public List getBooks(@RequestParam /* Add @Parameter here */ String author) {
        return List.of();
    }
}

Hint

Import @Parameter from io.swagger.v3.oas.annotations and add it before the author parameter with the description attribute.

Practice

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

easy

A. To describe method parameters for API documentation

B. To define database entity fields

C. To configure security roles

D. To handle exceptions globally

Solution

1. Step 1: Understand the role of @Parameter

   The @Parameter annotation is used to add descriptive information about method parameters in API endpoints.

2. Step 2: Differentiate from other annotations

   It is not used for database, security, or exception handling but specifically for API documentation clarity.

3. Final Answer:

   To describe method parameters for API documentation -> Option A

4. Quick Check:

   @Parameter describes API method parameters = D [OK]

Hint: Remember: @Parameter is for method parameter docs [OK]

Common Mistakes:

• Confusing @Parameter with @Schema for data models
• Thinking @Parameter manages security or exceptions
• Using @Parameter for database field mapping

2. Which of the following is the correct way to add a description to a method parameter using @Parameter?

easy

A. @Parameter(value = "User ID") String userId

B. @Parameter(description = "User ID") String userId

C. @Parameter(desc = "User ID") String userId

D. @Parameter(text = "User ID") String userId

Solution

1. Step 1: Recall the correct attribute name

   The @Parameter annotation uses the attribute description to add text about the parameter.

2. Step 2: Verify syntax correctness

   Only @Parameter(description = "User ID") String userId uses description correctly; others use invalid attribute names.

3. Final Answer:

   @Parameter(description = "User ID") String userId -> Option B

4. Quick Check:

   @Parameter uses description attribute = A [OK]

Hint: Use description= for @Parameter text, not value or desc [OK]

Common Mistakes:

• Using 'value' instead of 'description' attribute
• Using non-existent attributes like 'desc' or 'text'
• Omitting the attribute name entirely

3. Given the code snippet:

@Parameter(description = "User's age", required = true) int age

What effect does the required = true have in API documentation?

medium

A. Marks the parameter as mandatory in the API docs

B. Sets a default value for the parameter

C. Makes the parameter optional

D. Hides the parameter from the API docs

Solution

1. Step 1: Understand the required attribute

   The required = true flag indicates that the parameter must be provided by the API caller.

2. Step 2: Effect on API documentation

   This makes the parameter appear as mandatory in generated API docs, guiding users to supply it.

3. Final Answer:

   Marks the parameter as mandatory in the API docs -> Option A

4. Quick Check:

   required=true means mandatory parameter = B [OK]

Hint: required=true means parameter must be provided [OK]

Common Mistakes:

• Thinking required=true sets default values
• Assuming it hides the parameter
• Confusing required=true with optional parameters

4. Identify the error in this usage of @Schema annotation:

@Schema(description = "User's email", required = "true")
private String email;

medium

A. The annotation must be placed on the getter method, not the field

B. The description attribute is missing

C. The required attribute should be a boolean, not a string

D. The email field must be public for @Schema to work

Solution

1. Step 1: Check attribute types in @Schema

   The required attribute expects a boolean value, not a string.

2. Step 2: Identify the error in the code

   Using required = "true" is incorrect; it should be required = true without quotes.

3. Final Answer:

   The required attribute should be a boolean, not a string -> Option C

4. Quick Check:

   @Schema required must be boolean, not string = C [OK]

Hint: Use true/false without quotes for boolean attributes [OK]

Common Mistakes:

• Putting boolean values in quotes
• Assuming @Schema only works on methods
• Thinking field visibility affects @Schema

5. You want to document a complex API model field that can be null but has a maximum length of 50 characters. Which @Schema annotation usage is correct?

hard

A. @Schema(description = "Optional comment", maxLength = 50, nullable = false) private String comment;

B. @Schema(description = "Optional comment", maxLength = "50", nullable = "true") private String comment;

C. @Schema(description = "Optional comment", maxLength = 50, required = true) private String comment;

D. @Schema(description = "Optional comment", maxLength = 50, nullable = true) private String comment;

Solution

1. Step 1: Understand attribute types for @Schema

   Attributes like maxLength expect an integer, and nullable expects a boolean.

2. Step 2: Match requirements with options

   The field can be null, so nullable = true is needed, and maxLength should be 50 as an integer.

3. Step 3: Eliminate incorrect options

   @Schema(description = "Optional comment", maxLength = "50", nullable = "true") private String comment; uses strings for boolean and integer, which is wrong. @Schema(description = "Optional comment", maxLength = 50, required = true) private String comment; marks it required (not nullable). @Schema(description = "Optional comment", maxLength = 50, nullable = false) private String comment; sets nullable false, disallowing null.

4. Final Answer:

   @Schema(description = "Optional comment", maxLength = 50, nullable = true) private String comment; -> Option D

5. Quick Check:

   Use correct types and nullable=true for optional fields = A [OK]

Hint: Use boolean and int types correctly in @Schema attributes [OK]

Common Mistakes:

• Using strings instead of boolean or int for attributes
• Confusing nullable and required attributes
• Setting nullable false when field can be null