516

How do I test a RESTful PUT (or DELETE) method using cURL?

Syscall
  • 18,131
  • 10
  • 32
  • 49
John
  • 12,385
  • 14
  • 49
  • 72

5 Answers5

666

Using the -X flag with whatever HTTP verb you want:

curl -X PUT -d arg=val -d arg2=val2 localhost:8080

This example also uses the -d flag to provide arguments with your PUT request.

theabraham
  • 15,010
  • 7
  • 41
  • 41
174

Quick Answer:

In a single line, the curl command would be:

  1. If sending form data:

    curl -X PUT -H "Content-Type: multipart/form-data;" -F "key1=val1" "YOUR_URI"
    
  2. If sending raw data as json:

    curl -X PUT -H "Content-Type: application/json" -d '{"key1":"value"}' "YOUR_URI"
    
  3. If sending a file with a POST request:

    curl -X POST "YOUR_URI" -F 'file=@/file-path.csv'
    

Alternative solution:

You can use the POSTMAN app from Chrome Store to get the equivalent cURL request. This is especially useful when writing more complicated requests.

For the request with other formats or for different clients like java, PHP, you can check out POSTMAN/comment below.

POSTMAN to get the request code

Giacomo1968
  • 24,837
  • 11
  • 67
  • 96
Prateek
  • 5,714
  • 5
  • 21
  • 25
  • 6
    No idea why this has been downvoted... I copied here the idea how to pass JSON body for curl PUT. Also postman is pretty awesome tool to get curl code for more complicated queries :) – Mikael Lepistö Mar 30 '16 at 14:40
  • 2
    Thanks !! Even I don't have any idea why about the downvotes. Might be reluctance of the users to adopt it. I have created a respo of all my REST apis for mobile in POSTMAN and that is the best productivity tip that I can suggest to anyone working with REST. – Prateek Mar 31 '16 at 06:02
  • Real world example where I'm passing json data and parameter in the end point; curl -X PUT -H "Content-Type: application/json" -d '{"amount":"999","type":"car","parent_id":"12345"}' http://localhost:8080/transactionservice/transaction/2222 – vikramvi Sep 06 '17 at 05:14
  • "Content-Type" header itself makes makes a lot of difference whether your request is accepted or not. Postman is great at that. Many times the api developers themselves do not know what is the actual curl and postman comes to rescue there as well - to dubug the actual Content Type – Prateek Sep 06 '17 at 07:09
  • 1
    Having to install a complete browser (if one doesn't have Chrome) and an extension for it might be an overkill for some people imho. At least you could have provided an alternative for another more common (default installation) web browser like Firefox, where the HttpRequester does a similar job. – rbaleksandar Mar 02 '18 at 13:33
  • @rbaleksandar Postman can be installed as a standalone app as well. – Prateek Mar 02 '18 at 13:50
  • I did, it requires you to sign in. – rbaleksandar Mar 02 '18 at 13:59
  • 7
    It might be downvoted because the question is about curl. – tuxayo Jun 21 '18 at 13:39
  • It might be downvoted because it's non-libre/not open source and some people don't want to recommend such tools. Well I might be a bit dreaming there. There unfortunately not that much resistance to non-libre tools. But more importantly: downvotes shouldn't be used for that. – tuxayo Jun 21 '18 at 13:41
37

An example PUT following Martin C. Martin's comment:

curl -T filename.txt http://www.example.com/dir/

With -T (same as --upload-file) curl will use PUT for HTTP.

Tor Klingberg
  • 4,490
  • 6
  • 38
  • 50
  • 10
    Unfortunately, the `-T` is no substitute for `-X PUT` if you want to specify parameters with `-d` or `-F`. `-T` sends the content of a file via PUT. To achieve the `GET` after a redirect, add the parameter `--location` – Martin M Oct 23 '15 at 09:23
  • what if filename.txt is in remote server? – bosari Oct 08 '18 at 13:06
10
curl -X PUT -d 'new_value' URL_PATH/key

where,

X - option to be used for request command

d - option to be used in order to put data on remote url

URL_PATH - remote url

new_value - value which we want to put to the server's key

kalyani chaudhari
  • 6,807
  • 3
  • 23
  • 21
8

I am late to this thread, but I too had a similar requirement. Since my script was constructing the request for curl dynamically, I wanted a similar structure of the command across GET, POST and PUT.

Here is what works for me

For PUT request:

curl --request PUT --url http://localhost:8080/put --header 'content-type: application/x-www-form-urlencoded' --data 'bar=baz&foo=foo1'

For POST request:

curl --request POST --url http://localhost:8080/post --header 'content-type: application/x-www-form-urlencoded' --data 'bar=baz&foo=foo1'

For GET request:

curl --request GET --url 'http://localhost:8080/get?foo=bar&foz=baz'
sunitkatkar
  • 1,718
  • 1
  • 13
  • 11