Now, we want to use the browsable API to compose and send an HTTP DELETE request to our RESTful Web Service to delete an existing toy resource. First, go to the URL for an existing toy resource, such as http://localhost:8000/toys/7. Make sure you replace 7 with the id or primary key of an existing toy in the previously rendered Toy List. The HTML web page that displays the results of an HTTP GET request to /toys/7, plus additional details and controls, will be rendered.

At the right-hand side of the Toy Detail title, you will see a DELETE button. Click or tap this button. The web page will display a modal requesting confirmation to delete the toy resource. Click or tap the DELETE button in this modal.

The browsable API will compose and send an HTTP DELETE request to /toys/7 and we will see the results of the call in the web browser. The following screenshot shows a web browser displaying the HTTP status code 204 No Content in the response:

Now, go to the URL for the toys resource collection: http://localhost:8000/toys/. The HTML web page that displays the results of an HTTP GET request to /toys/ plus additional details and controls will be rendered. The recently deleted toy has been removed from the database. Thus, the list will not include the deleted toy.­ The following screenshot shows a web browser displaying the HTTP status code 200 OK in the response and the list of toys without the recently deleted toy:

The browsable API allowed us to compose and send many HTTP requests to our web service by clicking or tapping buttons on a web browser. We could check that all the operations are working as expected in our RESTful Web Service. However, we had to enter JSON content and we couldn't click on hyperlinks to navigate through entities. For example, we couldn't click on a toy's id to perform an HTTP GET request to retrieve this specific toy.

We will definitely improve this situation and we will take full advantage of many additional features included in the browsable API as we create additional RESTful Web Services. We will do this in the forthcoming chapters. We have just started working with the browsable API.