# FastAPI Response Model with SQLModel Now I'll show you how to use FastAPI's `response_model` with **SQLModel**. ## Interactive API Docs Up to now, with the code we have used, the API docs know the data the clients have to send: Interactive API docs UI This interactive docs UI is powered by Swagger UI, and what Swagger UI does is to read a big JSON content that defines the API with all the data schemas (data shapes) using the standard OpenAPI, and showing it in that nice UI. FastAPI automatically **generates that OpenAPI** for Swagger UI to read it. And it generates it **based on the code you write**, using the Pydantic models (in this case **SQLModel** models) and type annotations to know the schemas of the data that the API handles. ## Response Data But up to now, the API docs UI doesn't know the schema of the *responses* our app sends back. You can see that there's a possible "Successful Response" with a code `200`, but we have no idea how the response data would look like. API docs UI without response data schemas Right now we only tell FastAPI the data we want to receive, but we don't tell it yet the data we want to send back. Let's do that now. 🤓 ## Use `response_model` We can use `response_model` to tell FastAPI the schema of the data we want to send back. For example, we can pass the same `Hero` **SQLModel** class (because it is also a Pydantic model): ```Python hl_lines="3" # Code above omitted 👆 {!./docs_src/tutorial/fastapi/response_model/tutorial001.py[ln:33-39]!} # Code below omitted 👇 ```
👀 Full file preview ```Python {!./docs_src/tutorial/fastapi/response_model/tutorial001.py!} ```
## List of Heroes in `response_model` We can also use other type annotations, the same way we can use with Pydantic fields. For example, we can pass a list of `Hero`s. First, we import `List` from `typing` and then we declare the `response_model` with `List[Hero]`: ```Python hl_lines="1 5" {!./docs_src/tutorial/fastapi/response_model/tutorial001.py[ln:1]!} # Code here omitted 👈 {!./docs_src/tutorial/fastapi/response_model/tutorial001.py[ln:42-46]!} # Code below omitted 👇 ```
👀 Full file preview ```Python {!./docs_src/tutorial/fastapi/response_model/tutorial001.py!} ```
## FastAPI and Response Model FastAPI will do data validation and filtering of the response with this `response_model`. So this works like a contract between our application and the client. You can read more about it in the FastAPI docs about `response_model`. ## New API Docs UI Now we can go back to the docs UI and see that they now show the schema of the response we will receive. API docs UI without response data schemas The clients will know what data they should expect. ## Automatic Clients The most visible advantage of using the `response_model` is that it shows up in the API docs UI. But there are other advantages, like that FastAPI will do automatic data validation and filtering of the response data using this model. Additionally, because the schemas are defined in using a standard, there are many tools that can take advantage of this. For example, client generators, that can automatically create the code necessary to talk to your API in many languages. !!! info If you are curious about the standards, FastAPI generates OpenAPI, that internally uses JSON Schema. You can read about all that in the FastAPI docs - First Steps. ## Recap Use the `response_model` to tell FastAPI the schema of the data you want to send back and have awesome data APIs. 😎