SDET Unicorns

Delete Trello Card using Postman

Postman Delete Request

Table of Content

In the last few posts, we learned how to create a new card using the POST request, how to fetch a card using the GET request, and how to update the card using the PUT request. In this post, we will wrap it all up by deleting the card using the DELETE request.

Postman DELETE Request

Working with DELETE requests is always a bit tricky as unlike other HTTP methods you cannot make multiple same requests as that will throw an error of “resource not found”. Let’s take a look at an example –

In the image below, I am deleting an existing Trello card and I got a 200 OK response confirming that the data was deleted successfully.

image 1

When attempting to hit the same request again, I got a 404 Not Found error (as seen in the image below).

image 2

Therefore, when planning on writing your API tests, you need to structure your data in such a way where you get a new resource every time when you are deleting a resource (we will look into this in the upcoming posts).

Check out the video below to learn more about how to work with DELETE request in Postman –

To learn about API Test Automation using JavaScript, check out my free tutorial series here –

JavaScript API Test Automation Tutorial Series

I hope this post helped you out, let me know if you have any questions in the comments below!

Happy testing! 

My Resources

Thrive Suite: The all-in-one WordPress theme I used to create my blog.
Jasper AI: My favorite AI writing tool.
Surfer SEO:  A tool to help you rank your content on the first page of Google.

Write Content Faster


Write blog posts that rank for affiliate terms!

Join our mailing list

Unlock the Secrets to Becoming a SDET Pro in the Industry!

Stay ahead of the curve! Join our mailing list for exclusive insights, tips, and the latest industry updates delivered straight to your inbox

Table of Content

Related Post

Functional vs Regression Testing

Functional Testing vs Regression Testing: Main Differences

Testing has increasingly become a requirement in the software development lifecycle in recent years. The realization that development is no longer a focal point for stakeholders but saving costs by catching defects early in their application makes it necessary to learn different testing types.

Read More »