diff --git a/apps/docs/src/contents/03.developer-guide/04.BuildingAPI.mdx b/apps/docs/src/contents/03.developer-guide/04.BuildingAPI.mdx index 7d5dc4ff9..e5afd40c7 100644 --- a/apps/docs/src/contents/03.developer-guide/04.BuildingAPI.mdx +++ b/apps/docs/src/contents/03.developer-guide/04.BuildingAPI.mdx @@ -168,7 +168,7 @@ Finally, in the routing file located at src/core/routes/app.routes.ts ## Data Input -LifeForge's approach to taking data input is slightly different from tRPC, where there is only one channel for all the parameters. In LifeForge, the input is divided into two parts: query, body. Queries are basically the URL search parameters, the part after the ? in the URL, while body is the request body, which is usually in JSON format or form data. For those who are familiar with RESTful APIs, these should be familiar concepts. +LifeForge's approach to taking data input is slightly different from tRPC, where there is only one channel for all the parameters. In LifeForge, the input is divided into two parts: query and body. Queries are basically the URL search parameters, the part after the ? in the URL, while body is the request body, which is usually in JSON format or form data. For those who are familiar with RESTful APIs, these should be familiar concepts. The division of input into query and body is based on the HTTP method used. For GET requests, only query parameters are accepted, while for POST requests, both query and body parameters are accepted. This design choice is made to adhere to the semantics of HTTP methods, where GET requests are meant for retrieving data and should not have a request body, while POST requests are meant for creating or updating data and can have a request body.