Gain insights into using Python to consume and create REST APIs, delving into HTTP methods like GET and PUT. Ideal for enhancing intermediate Python skills.

Flask.tar.gz

Get Products

Get Product

Create Product

Update Product

Delete Product

Product OPTIONS

REST is the most used mechanism to publish APIs for general consumption. Each language has its own set of libraries and methods that help a developer consume these APIs. This course will teach you how to use Python and its libraries for consuming and creating REST APIs in the easiest way possible.

In the first part of this course, you’ll learn how to work with Python in using REST APIs for various scenarios. Then, in the second part, you’ll focus on building your own REST APIs using the HTTP methods, including GET, PUT, etc.

This course is geared toward intermediate users who have a basic understanding of Python and want to improve their skills in using existing REST APIs and building their REST API implementations.

Python REST API Development: A Comprehensive Guide

To update an existing entry in the collection, we use the PUT method. 

# Updating an existing product

#key# According to the specifications:RFC2616 #key#, “The PUT method requests that the enclosed entity be stored under the supplied Request-URI. If the Request-URI refers to an already existing resource, the enclosed entity SHOULD be considered as a modified version of the one residing on the origin server. If the Request-URI does not point to an existing resource, and that URI is capable of being defined as a new resource by the requesting user agent, the origin server can create the resource with that URI. If a new resource is created, the origin server MUST inform the user agent via the 201 (Created) response.”

So, PUT can be used for creating a new product as well as updating an existing product. However, creating a new product using PUT is not generally recommended or practised.

Based on the above definition, the following are the main features of the PUT method:

* The Request-URI refers to an existing item.
* The entity provided within the body has to be used to update the existing item referred to via the resource URI.
* PUT is idempotent, i.e., multiple PUT requests with the same data will result in the same effect on the server as a single PUT request.
* If the updating of an existing entity is encapsulated in a long process, then the initial response will be `202 ACCEPTED`, with a URI to know the current status. The status URI should send either `200 OK` if the operation is successful, or send the corresponding error otherwise.
* The request and the response can't be cached.

Understand the PUT method and design the products API to update an existing product.

Introduction

Client

Server

Project: Tickets API

Conclusion

Design the PUT Endpoint for Updating an Existing Product

Updating an existing product