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

The delete operation in the REST world doesn't guarantee the deletion of the specific entry by the server. The server may choose to mark it as deleted for the future or consider it as an entry that is no longer accessible. With that in mind, let's delve into the details of the DELETE method.

# Removing an existing product

The W3C specification states that “The DELETE method requests that the origin server delete the resource identified by the Request-URI. This method may be overridden by human intervention (or other means) on the origin server. The client cannot be guaranteed that the operation has been carried out, even if the status code returned from the origin server indicates that the action has been completed successfully. However, the server should not indicate success unless, at the time the response is given, it intends to delete the resource or move it to an inaccessible location.”

According to the description above, the DELETE method has the following features:

* It's idempotent. That means if we send the same request (to the same URI with the same parameters) any number of times, it'll always result in the same effect on the server.
* DELETE requests don't need to actually delete the resource or entry. However, it should make the resource/entry unreachable.
* The server can override the request. This means that the server can decide not to process the DELETE request.
* The server should send `200 OK` only if the response contains data in the body that describes the status. If no data is sent in the body, then `204 NO CONTENT` should be sent as the value of status. However, the general practice is to send `200 OK` with no body.
* The response is not cacheable.

Understand the DELETE method and design the products API to delete an existing product.

Introduction

Client

Server

Project: Tickets API

Conclusion

Design the DELETE Endpoint for Removing an Existing Product

Removing an existing product