Summary
It is a fairly safe assumption that all web APIs require some input from users at some point. Even APIs that are read-only often might allow for filtering, searching, or paginating data. Therefore, to become proficient at building web applications in general, and Sanic applications specifically, you must learn the data tools at your disposal.
In this chapter, we covered a great deal of material. We learned how to pull data from headers, cookies, and the request body. When using headers, form data, query arguments, and file data, we discovered that these objects could operate as regular dictionaries or dictionaries of lists to be both compliant with HTTP standards and also usable for most regular use cases. Additionally, we saw that the request body itself could be sent as a single chunk or in multiple chunks.
However, perhaps the biggest takeaway is that reading data cannot and does not take a single path. As a reminder, Sanic provides the tools to build the most obvious...
