SDET Unicorns

Write API Tests for HTTP PUT Method

Table of Content

Similar to the HTTP POST method, the HTTP PUT method also takes in the request payload but instead of creating a new resource, it lets the user update the existing resource.

The difference between the PUT and POST method is that PUT is idempotent i.e you can keep calling the same request multiple times but it won’t have any side effects, unlike a POST request.

Let’s take a look at an example of a PUT request below –

it('PUT /users/:id', () => {
  // data to update
  const data = {
    status: 'Active',
    name: `Luffy - ${Math.floor(Math.random() * 9999)}`,

  return request
    .set('Authorization', `Bearer ${TOKEN}`)
    .then((res) => {

The above code will generate a result similar to this –

  code: 200,
  meta: null,
  data: {
    id: 132,
    name: 'Luffy - 7568', // name updated
    status: 'Active', // status updated
    email: '',
    gender: 'Female',
    created_at: '2020-10-05T03:50:06.247+05:30',
    updated_at: '2020-10-06T00:34:22.958+05:30'

There you go, that’s all we need to do to create an API test for the HTTP PUT method. 🙌

Check out this video to see a detailed explanation on how to work with the HTTP PUT method:

You can also clone the GitHub repo to access this code

To learn more about API testing, check out my free tutorial series here –

JavaScript API Automation Testing Tutorial Series

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 »